VirusTotal
17 / 91 engine detections
보고서 열기“Phishing Simulation Landing Page”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@phishingbox.com.
The latest stored availability evidence still shows the domain reachable; 27 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
wwww-linkedin.be — 마지막으로 알려진 활성 (HTTP 200). 브랜드 사칭: LinkedIn; 사기 유형: Impersonation. 증거 요약: VirusTotal 17/91 (Criminal IP, BitDefender, Chong Lua Dao, CyRadar, ESET); URLQuery 3 det.; URLScan malicious verdict; 1 external blocklist match (Phishunt); CF Radar malicious; PhishDestroy score 100/100. 등록기관: Key-Systems.
원본 포렌식 기록을 보존하기 위해 아래의 상세 PhishDestroy AI 분석은 영어로 유지됩니다.
17 / 91 engine detections
보고서 열기3 det.
보고서 열기악성
보고서 열기악성
보고서 열기5 community references
보고서 열기No threat flag
보고서 열기Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
AI-assisted evidence review
wwww-linkedin.be returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-21, and its registration date is listed as 2021-06-08.
Phishunt included wwww-linkedin.be on its blocklist as of 2026-10-01. VirusTotal recorded 17 detections out of 91 scanners on 2026-09-30. OTX showed 5 pulses on 2026-09-22. The SSL certificate from Let's Encrypt / YE1 was scanned on 2026-09-21, and the internal listing was true on that date.
The evidence from Phishunt, VirusTotal, and OTX was recorded on separate dates, so their observations reflect different points in time. The SSL scan and internal listing were captured earlier than the HTTP check, indicating that subsequent observations may differ from initial findings. Comparing these sources requires attention to their respective dates rather than assuming simultaneous results.
For wwww-linkedin.be, retain all dated evidence, including the Phishunt blocklist entry, VirusTotal detections, and OTX pulses, for reference. Compare future observations against these records to track any changes. Avoid submitting sensitive information during review of wwww-linkedin.be, and ensure all evidence is preserved for ongoing assessment.
Last checked
ns1.intelliwire.netns2.intelliwire.netns3.intelliwire.commail.wwww-linkedin.bepriority 10Location describes the IP network.
1f55cd3e47c6d10405ccca639e33f129c88e40848bf8a2975c1e1a4ae983a381Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
mail.wwww-linkedin.beDomain recordwww.wwww-linkedin.beDomain recordThe original observation time is not recorded for these hostnames.
Google PageSpeed Insights — mobile performance audit of wwww-linkedin.be · checked Sep 21, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
wwww-linkedin.be
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
알 수 없음→live_content
content_served
17→15
15→17
접속 가능
No threat flag
View source17/91 engine detections
View source5 community references
View sourcePD-20260921-91907F
Page captured
View sourcewwww-linkedin.be
View sourcePD-20260921-91907F Recipient: abuse@phishingbox.com 계정 자격 증명, 개인 정보 또는 결제 정보를 입력했거나 이 도메인에서 파일을 다운로드한 경우 즉시 조치를 취하세요. 다음은 사건을 신고하고 자신을 보호하는 데 도움이 되는 리소스입니다.
공식 사이버 범죄 연락처 또는 불만사항 초안 작성 →를 받으려면 국가를 선택하세요.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
wwww-linkedin.be)비록 모든 세부 사항을 알지 못하더라도 — 어쨌든 신고를 하세요. 부분적인 정보라도 수사에 도움이 됩니다.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.