VirusTotal
5 / 91
“fortnovax.com”
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.
5 / 91
DBL_SPAM
checked — no detections recorded
Report4 community references
Reportprovider verdict: clean
Reportstored report
Report Analysis completed
Report80/100
ReportChecked; no threat flag recorded
Reportfortnovax.com returned an HTTP status 200 on 2026-10-01, a dated response recorded during an HTTP check. The domain was first observed on 2026-09-19, according to the recorded evidence timeline.
The domain was first observed on 2026-09-19, and an HTTP check on 2026-10-01 returned status 200. VirusTotal recorded 5 detections across 91 scanners on 2026-09-30, while OTX listed 4 pulses on 2026-09-20. The PhishDestroy internal listing was true, and the registration date was 2026-06-07 with PDR Ltd. d/b/a PublicDomainRegistry.com as registrar. A PageSpeed check on 2026-09-19 produced a performance score of 73, and the SSL certificate was issued by Let's Encrypt / YE2 on 2026-09-19.
The PhishDestroy internal listing and the OTX pulses reflect observations made on different dates, so their counts cannot be compared directly. VirusTotal detections on 2026-09-30 and the HTTP status on 2026-10-01 were recorded later than the first observation on 2026-09-19, meaning the records describe separate points in time rather than one continuous state.
Reviewers should retain the dated records for fortnovax.com, including the HTTP check, VirusTotal result, and OTX pulses, so later observations can be compared against them. Avoid submitting sensitive information while examining fortnovax.com, and compare any new dated observations with the existing evidence rather than relying on a single snapshot.
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
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
5729c64fe48e54ca96fe3c79f77cc613be0029a2ff1abfbafdc43494558b056cSaved 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 fortnovax.com · checked Sep 19, 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-20260919-ED049D 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 (NL): Dutch Criminal Code - Article 326 (Computer Fraud) Dutch Criminal Code - Article 326c (Phishing) GDPR Netherlands law explicitly criminalizes phishing and computer fraud. 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