VirusTotal
9 / 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; 22 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 | fortgz.top |
malicious | Sinkholed |
fortgz.top returned an HTTP status code of 200 in a check recorded on 2026-10-01, indicating a successful response at that time. The domain is also listed in the PhishDestroy internal catalogue.
VirusTotal, checked on 2026-09-29, reported 9 detections out of 91 scanners for fortgz.top. OTX was checked on 2026-09-18 and showed 4 pulses. The domain was first observed on 2026-09-16, with a PageSpeed performance score of 71 recorded the same day. An SSL scan on 2026-09-16 identified Let's Encrypt / YR2 as the certificate issuer. The registrar was recorded as PDR Ltd. d/b/a PublicDomainRegistry.com on 2026-09-02.
The evidence provides separate dated records from HTTP, VirusTotal, OTX, PageSpeed, and SSL sources. Each observation reflects a distinct aspect of fortgz.top, allowing for a comprehensive comparison of technical and security-related measurements. The chronology of the checks shows that the domain was observed and checked over a period of several days, but the records do not indicate a specific event or outcome.
For fortgz.top, retain the HTTP, VirusTotal, OTX, PageSpeed, and SSL records for ongoing reference. Compare future VirusTotal and OTX checks to these records to monitor any changes in detections or pulses. Review subsequent HTTP and PageSpeed checks to observe any variation in response or performance.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Scanner note: alive_content: raw=ok; http=200; via=https_proxy
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.
1e7f2c8da4a1ad8b28a9ed7416d82594a8fa3ddb1a0eda49dd07e6446e11c32cSaved 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 fortgz.top · checked Sep 16, 2026
46.29.26.38. 12 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-20260916-2E6442 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 (CA): Criminal Code Section 342.1 Criminal Code Section 380 - Fraud PIPEDA Canadian law prohibits computer fraud and unauthorized access. 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