VirusTotal
5 / 92
bitgetassetpolicy.com returned an HTTP 403 status on 2026-10-08, indicating restricted access at that time. The domain’s PageSpeed performance score of 94 was recorded on 2026-10-07.
OTX referenced bitgetassetpolicy.com in 3 pulses as of 2026-10-08. VirusTotal scanned the domain on 2026-10-07 with 0 detections out of 92 scanners. The domain was registered on 2026-09-29 with NICENIC INTERNATIONAL GROUP CO., LIMITED and uses a Let's Encrypt / YE2 SSL certificate. PhishDestroy internally listed the domain.
The recorded observations span security, reputation, and performance metrics for bitgetassetpolicy.com. The HTTP 403 response and PageSpeed score were captured within one day of each other, while OTX pulses and VirusTotal results provide additional dated context.
Retain the dated HTTP status, VirusTotal scan, OTX pulses, and PageSpeed score for bitgetassetpolicy.com. Use these source records to compare future checks and identify any changes in accessibility or performance.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: cloudflare_challenge: raw=cf_challenge; http=403; via=https_proxy; server=cloudflare
Edge-IP reputation is not attributed to this domain.
mustafa.ns.cloudflare.comLocation describes the IP network.
9ae5006a58be4e7f3224f157c2cd2ce19c6b001e73d7002ebaadb31b1d65ffbaSaved 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 bitgetassetpolicy.com · checked Oct 7, 2026
188.114.97.1. 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