VirusTotal
17 / 89
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 1 month 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.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| OpenDNS | azure-dash.com |
phishing | Phishing Block |
| Cloudflare DNS | azure-dash.com |
malicious | Sinkholed |
| DNS4EU | azure-dash.com |
malicious | Sinkholed |
| DigiCert UltraDNS | azure-dash.com |
malicious | Sinkholed |
| Quad9 DNS | azure-dash.com |
malicious | Sinkholed |
On 2026-10-01, azure-dash.com returned an HTTP status code of 200 in a recorded observation. The domain was first observed on 2026-09-10, and its registration date is recorded as 2025-10-28.
A PhishDestroy internal listing for azure-dash.com is recorded as true. The OTX check on 2026-09-10 recorded 5 pulses, while the VirusTotal check on 2026-09-18 recorded 17 detections across 89 scanners. The SSL certificate was scanned on 2026-09-11 with issuer Google Trust Services / WE1, and the registrar is Dynadot Inc. The PageSpeed check on 2026-09-10 returned a performance score of 98.
The OTX and PageSpeed observations share the 2026-09-10 date, while the SSL scan, VirusTotal check, and HTTP check fall on later dates, so these records describe different points in time rather than one snapshot. The PhishDestroy internal listing and the VirusTotal detections come from separate sources with separate collection dates, which limits direct comparison between them. Because the observation dates differ, a reader should treat each record as dated rather than current.
Anyone reviewing azure-dash.com should retain the dated records and note each source and timestamp before comparing later observations. Subsequent checks of azure-dash.com should be matched against the same source labels and dates to show change over time. During review, avoid submitting sensitive information to azure-dash.com or relying on any single dated record as a current description.
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.
conrad.ns.cloudflare.comjosephine.ns.cloudflare.comLocation describes the IP network.
bc053e170e4f45d91c670e749466c1361558fc984f1f216ce7646d175f64f291Saved 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 azure-dash.com · checked Sep 10, 2026
104.21.87.14. 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.
PD-20260910-EA3532 Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
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