VirusTotal
6 / 91
Interpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“301 Moved Permanently”
Assessment based on the stored source evidence below. Review sources →
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.
6 / 91
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
3 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.
80/100
A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
Stored narrative · generated . Provider checks below retain their own observation dates.
falconsgg.cc returned an HTTP status code 301 on 2026-10-01, according to the recorded HTTP check. The same domain appears in the PhishDestroy internal catalogue, and its first observation is dated 2026-09-17.
The HTTP check on 2026-10-01 recorded a 301 response for falconsgg.cc. VirusTotal, checked on 2026-09-25, recorded 6 detections across 91 scanners. OTX, checked on 2026-09-25, listed 3 pulses. The SSL certificate was scanned on 2026-09-23 and issued by Google Trust Services / WE1. The registration date is recorded as 2026-09-04 with Dynadot Inc as registrar.
The recorded HTTP response describes only the reply captured on its check date, while the VirusTotal and OTX entries reflect separate observations made on their own dates. Because the checks fall on different days, the records can be read as a chronology of collection rather than a single measurement. The PhishDestroy internal catalogue and the first observation add further dated reference points for the same domain.
For falconsgg.cc, preserve the HTTP check record and the PhishDestroy internal catalogue entry as separate source documents. Retain the VirusTotal and OTX results alongside them, and compare later HTTP responses and scanner results against these saved records. Keep the first observation record so the collection timeline remains traceable.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://falconsgg.cc/; server=cloudflare
Edge-IP reputation is not attributed to this domain.
janet.ns.cloudflare.comLocation describes the IP network.
01160753a71ab9c90cb2a87f9aff8f61bbeb5252379af005040412bb775eb3ebSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
188.114.96.9.7 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.
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