VirusTotal
7 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
Assessment based on the stored source evidence below. Review sources →
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@globaldomaingroup.com.
The latest stored availability evidence still shows the domain reachable; 29 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.
These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.
7 / 91
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
DBL_SPAM
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
checked — no detections recorded
ReportAlerts refer to the preserved scan. They do not describe the current state of the site.
4 community references
ReportCommunity publication references, not a vendor verdict or evidence of a common operator.
provider verdict: clean
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
stored report
View stored capture ↗ ReportA preserved page image documents what the collector received; a capture is not a safety verdict.
Analysis completed
ReportThis is the recorded automated analysis. Completion alone is not a safety verdict.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
0 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.
fortgaves.com returned HTTP status 200 on 2026-10-01, according to the recorded HTTP check. The domain was first observed on 2026-09-16, and its registration date is recorded as 2026-09-03.
The PhishDestroy internal listing records fortgaves.com as listed, with that listing present in the evidence set. VirusTotal recorded 7 detections across 91 scanners on 2026-09-29. OTX recorded 4 pulses on 2026-09-19. The SSL certificate was issued by Let's Encrypt / YE2 and scanned on 2026-09-17. The registrar is recorded as Global Domain Group LLC, and the PageSpeed performance score was 75 on 2026-09-16.
The PhishDestroy listing, VirusTotal detections, and OTX pulses were each recorded on different dates, so their counts reflect separate snapshots rather than one synchronized measurement. Because the HTTP check, SSL scan, and PageSpeed score also carry distinct dates, a reader can compare the sequence of observations without treating any single record as a current state. The named sources provide overlapping but non-identical views, and their differing timestamps limit direct comparison of their values.
Retain the dated records for fortgaves.com, including the PhishDestroy listing, VirusTotal result, OTX pulses, and SSL scan, so later observations can be compared against them. When reviewing the domain, compare each new dated observation with the corresponding earlier record rather than combining values from different dates. Avoid submitting sensitive information during any review of fortgaves.com until the recorded evidence has been independently assessed.
21 · datasets with records / 10 · not recorded
What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.
These checks have no retained result. This does not mean they passed or that a scan is running.
0 · external source matches
Global Domain Group LLC · 46.29.26.38 · DNS, TLS and retained responses
a.dnspod.comb.dnspod.comc.dnspod.comLocation describes the IP network.
8ac073f127663b19b11cb3a5dc30cc533ac94fa44a1f7e52a8abc59d5154dec6Saved 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 fortgaves.com · checked Sep 16, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Stored browser and crawler observations
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='fortgaves.com', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
1 · outbound report records
46.29.26.38.Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
Unknown→dns_inactive
dns_nxdomain
dns_inactive→Unknown
probe_inconclusive
live_content→dns_inactive
dns_nxdomain
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
live_content→Unknown
stale_current_evidence
Unknown→live_content
content_served
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
live_content→Unknown
probe_inconclusive
Unknown→live_content
content_served
Unknown
probe_inconclusive
5→6
4→5
3→4
2→3
0→2
Reachable
16 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.
Shared hosting, registrar records and related domains
Original reports, independent checks and evidence links
PD-20260916-534F93 Recipient: abuse@globaldomaingroup.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 (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. 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.
Recovery steps, reporting contacts and complaint drafts
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
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
fortgaves.com)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
Stored evidence snapshot. Source timestamps appear where available.
VirusTotal detections for fortgaves.com: 7 (2026-09-29 02:19:25 UTC).
Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.
submit an appeal or review the FAQ page.