VirusTotal
9 / 92
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 7 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.
9 / 92
DBL_SPAM
Report stored; detailed verdict not recorded
Report4 community references
Reportprovider verdict: suspicious
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
ReportThe domain fortgx.live was recorded with an HTTP 301 status on 2026-10-08, indicating a response that directed clients elsewhere at that time. The domain was also included in the PhishDestroy internal listing, providing an additional record of its presence in a security-related catalogue.
On 2026-10-08, fortgx.live returned an HTTP 301 response. VirusTotal checked the domain on 2026-09-30 and reported 5 detections out of 92 scanners. OTX included fortgx.live in 4 pulses as of 2026-10-08. The PhishDestroy internal listing also referenced the domain. The registrar was Dynadot Inc, and the SSL certificate was issued by Let's Encrypt / YR2, with the certificate scan occurring on 2026-10-07.
The source records present a technical and security-focused profile for fortgx.live, with each observation reflecting a specific aspect of its status. The HTTP 301 response documents the server's behavior on a particular date, while VirusTotal and OTX show that the domain has been noted by multiple security monitoring services. The PhishDestroy internal listing further adds to the record, highlighting that the domain has been catalogued for reference by the publisher.
To evaluate fortgx.live, retain the HTTP response and VirusTotal records for future comparison. Review the OTX pulse entries and PhishDestroy internal listing to monitor any changes in how the domain is referenced by these sources. Use the dated evidence to inform subsequent decisions and track the domain's status over time.
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.
74cff2dcf01766f1c1692dbe07c3682ac63cae293169b109a9f9215f1221f4abSaved 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 fortgx.live · checked Oct 6, 2026
46.29.26.38. 11 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-20261006-8119D1 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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