VirusTotal
4 / 92
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@publicdomainregistry.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.
4 / 92
DBL_SPAM
Report stored; detailed verdict not recorded
Report3 community references
Reportprovider verdict: suspicious
Reportstored report
Report Analysis completed
ReportChecked; no threat flag recorded
Reportfortfind.icu was included in the PhishDestroy internal listing and received a PageSpeed performance score of 72, both recorded on 2026-10-06. OTX also recorded three pulses for this domain on the same date, highlighting its presence in multiple monitoring sources.
OTX documented three pulses related to fortfind.icu on 2026-10-06. VirusTotal checked the domain on 2026-09-25, reporting zero detections out of 92 scanners. The PhishDestroy internal listing included fortfind.icu as of 2026-10-06. A PageSpeed check on 2026-10-06 reported a performance score of 72. The domain was registered on 2026-09-25 with PDR Ltd. d/b/a PublicDomainRegistry.com.
These records show that fortfind.icu has been observed by several monitoring platforms, each providing a different perspective. OTX pulses suggest that the domain has been noted in community reporting, while VirusTotal found no detections during its scan. The PageSpeed score and inclusion in the PhishDestroy internal listing add technical and reputational context to its profile.
To evaluate fortfind.icu, consult the OTX pulse records and VirusTotal scan as primary references. Retain the PhishDestroy internal listing and PageSpeed performance data for ongoing comparison. Preserve all dated source records for future monitoring and to track any changes in the domain’s profile.
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='fortfind.icu', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.
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.
23df353beb5775b07f79753f1c1f2c94686ff049bceafd900929295552e48d12Saved 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 fortfind.icu · checked Oct 6, 2026
46.29.26.38. 10 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-5E1A64 Recipient: abuse@publicdomainregistry.com 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 (GB): Computer Misuse Act 1990 Fraud Act 2006 Communications Act 2003 - Section 127 UK law criminalizes unauthorized computer access, fraud, and malicious communications. 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