VirusTotal
5 / 91
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@ufocorp.net.
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
malicious
ReportDBL_SPAM
checked — no detections recorded
Report4 community references
Reportprovider verdict: clean
Reportstored report
Report Checked; no threat flag recorded
Reportfortolo.top returned HTTP status 200 in an HTTP check recorded on 2026-10-01, indicating a successful response on that date. The evidence also shows that the domain was first observed on 2026-09-19.
The HTTP check on 2026-10-01 recorded status 200 for fortolo.top. VirusTotal, checked on 2026-09-30, reported 5 detections out of 91 scanners. OTX, checked on 2026-09-20, listed 4 pulses for the domain. The domain appears in the PhishDestroy internal listing. Its registration date is 2026-08-02 with registrar PDR Ltd. d/b/a PublicDomainRegistry.com. The SSL scan on 2026-09-19 identified the issuer as Let's Encrypt / YE2. PageSpeed on 2026-09-19 returned a performance score of 74.
These records provide a timeline of technical and security-related observations for fortolo.top, with each source documenting its own findings on separate dates. The HTTP response, VirusTotal, OTX, and PhishDestroy entries each reflect distinct aspects of the domain's recorded history. The SSL and PageSpeed results further supplement the technical profile without indicating content or intent.
Review the VirusTotal and OTX records for fortolo.top as separate source documents to track security-related observations. Compare the HTTP response record with the first-observation entry to understand the domain's timeline. Retain the PhishDestroy listing and other technical records for comprehensive future reference.
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='fortolo.top', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("SO
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.
b9bfcadef5cb23e4b676a750c09e96e63e5ac2e390cfcf9262d471d6b5b81b52Saved 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 fortolo.top · checked Sep 19, 2026
109.238.86.76. 13 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-4D426E Recipient: abuse@ufocorp.net 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 (US): 18 U.S.C. § 1343 - Wire Fraud 18 U.S.C. § 1030 - Computer Fraud and Abuse Act (CFAA) 15 U.S.C. § 45 - FTC Act (Deceptive Practices) Federal laws prohibit wire fraud, computer fraud, and deceptive business practices. 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