VirusTotal
5 / 89
“DityBit - Mobile Crypto Exchange Preview”
ditybit.us was observed on 2026-10-01 with entries on both the MetaMask and SEAL external blocklists, according to the evidence. The domain received a PageSpeed performance score of 95 on 2026-08-28, highlighting a recorded technical metric.
VirusTotal reported 5 detections out of 89 scanners for ditybit.us on 2026-09-11. OTX listed 4 pulses as of 2026-08-31, while the SSL certificate was issued by Google Trust Services / WE1 and scanned on 2026-08-29. The domain was first observed on 2026-08-28 and registered the previous day, 2026-08-27. Internal listing by Phishdestroy was also noted as true.
The evidence draws from several sources, each with its own observation date, allowing for comparison across time. The blocklist entries, VirusTotal detections, OTX pulses, and SSL scan reflect distinct snapshots, which may not align in their coverage of the domain's status. Comparing these records can help identify changes or consistencies in the domain's profile.
Retain all dated evidence for ditybit.us, including source names and timestamps, to support future reviews. Compare subsequent observations directly to these baseline records and avoid submitting sensitive information during ongoing evaluation. Each new check should be documented separately from the original evidence set.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
Edge-IP reputation is not attributed to this domain.
igor.ns.cloudflare.comjill.ns.cloudflare.comsmtp.google.compriority 1Location describes the IP network.
56195742a356074a34343403c9e589365aa3d0076ec62ca5cb1b620bb844b224Saved 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 ditybit.us · checked Aug 28, 2026
104.21.54.235. 15 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