VirusTotal
15 / 92
ReportInterpretation & limits
Engine detections from this stored analysis. Vendors and collection times may differ from other sources.
“Google”
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.
15 / 92
ReportEngine detections from this stored analysis. Vendors and collection times may differ from other sources.
2 external matches
DetailsA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
9 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.
Checked; no threat flag recorded
ReportA result applies to the recorded source and observation time. Absence of a flag is not proof of safety.
PhishDestroy first observed bitrgift.com on Oct 15, 2026. Stored content metadata identifies Google as the apparent target. The captured page title is “Google”. Stored page analysis classifies the content as impersonation. Current evidence score: 100/100 (critical).
Positive findings are stored from 3 sources: VirusTotal, MetaMask, and SEAL. VirusTotal recorded 15 detections among 92 engines: ChainPatrol, alphaMountain.ai, BitDefender, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky, Lionic, SOCRadar, Sophos, VIPRE on Oct 15, 2026 at 16:55 UTC. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 15, 2026 at 14:20 UTC. Additional recorded evidence: AlienVault OTX listed 9 community pulse references (not vendor detections) on Oct 15, 2026 at 16:55 UTC. URLScan captured the page on Oct 15, 2026 at 15:54 UTC.
The collector marked the hostname reachable on Oct 15, 2026 at 15:54 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause probe inconclusive on Oct 15, 2026 at 13:54 UTC. Registration records for the domain list NICENIC INTERNATIONAL GROUP CO., LIMITED as the registrar and Sep 6, 2026 as the creation date. At collection time, the hostname resolved to 62.60.226.163. The evidence archive retains 2 visual captures from PhishDestroy and URLScan. TLS metadata lists Let's Encrypt / YR2 as the certificate issuer with validity through Dec 5, 2026; checked Oct 15, 2026 at 16:02 UTC.
The content indicators and 3 positive source findings support the current Google-themed impersonation classification.
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.
martin.ns.cloudflare.comsunny.ns.cloudflare.comLocation describes the IP network.
40dcf5b7b7e2740681612adfbd64fa68d0c46379db638443bdcf0e3c97af2cc6www.bitrgift.comSaved 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 bitrgift.com · checked Oct 15, 2026
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
http://bitrgift.com/https://www.google.com/Content-Type: text/html; charset=UTF-8Cache-Control: private, max-age=0Content-Encoding: gzipServer: gws8720df457a93b97d3cdd7c05714c8e255a1969085844eb247756b869dbea636aSec-CH-Prefers-Color-Schemeh3=":443"; ma=2592000,h3-29=":443"; ma=2592000private, max-age=0gzipobject-src 'none';base-uri 'self';script-src 'nonce-43c96ba7wtGvNdQvpA7UBQ' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hptext/html; charset=UTF-8same-origin-allow-popups; report-to="gws"Thu, 15 Oct 2026 15:55:35 GMT-1; rel="compression-dictionary"CP="This is not a P3P policy! See g.co/p3phelp for more info."unload=(){"group":"gws","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/gws/other"}]}gwschunkedSAMEORIGIN0Values retained by the collector; long values may be shortened during collection.
Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.
/robots.txt
A legacy response is stored, but it does not establish whether the file exists.
/sitemap.xml
A legacy response is stored, but it does not establish whether the file exists.
/.well-known/security.txt
A legacy response is stored, but it does not establish whether the file exists.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Local archived 2026-10-15 15:55:36 UTC62.60.226.163.11 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