VirusTotal
7 / 91
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@forticore.digital.
The latest stored availability evidence still shows the domain reachable; 24 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DNS4EU | fortnitelock.top |
malicious | Sinkholed |
fortnitelock.top returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-19, and its registration date is listed as 2026-08-27.
The HTTP check on 2026-10-01 recorded status 200 for fortnitelock.top. A PhishDestroy internal listing was recorded, and the blocklist check is dated 2026-10-01. VirusTotal recorded 6 detections across 89 scanners as of 2026-09-24. OTX recorded 4 pulses on 2026-09-20. The SSL certificate was scanned on 2026-09-19 and issued by Let's Encrypt / YR2. The registrar is PDR Ltd. d/b/a PublicDomainRegistry.com.
The HTTP, VirusTotal, OTX and SSL observations carry different dates, so they describe separate moments rather than one synchronized snapshot. The PhishDestroy listing and the blocklist check share a date, while the VirusTotal and OTX records were captured earlier. Because these named sources were checked at different times, direct comparison between them should account for the gap between observation dates.
Retain dated copies of each observation for fortnitelock.top, including the HTTP check, VirusTotal result, OTX pulses and PhishDestroy listing. Compare later observations against these records to see whether the recorded values change over time. Avoid submitting sensitive information during any review of fortnitelock.top until the relevant records have been examined.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='fortnitelock.top', port=80): Max retries exceeded with url: / (Caused by NewConnectionErro
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
1c75dc02f0f14b716c5e20726ce13daee977e208806ad86f3a3a46398e6ae8b2Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of fortnitelock.top · checked Sep 19, 2026
46.29.26.38. 16 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
PD-20260919-F09205 Recipient: abuse@forticore.digital Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (RU): Russian Criminal Code Article 159.6 (Computer Fraud) Russian Criminal Code Article 272 Federal Law on Information Russian law criminalizes computer fraud and unauthorized access to information systems. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive