VirusTotal
4 / 91
“dark.direct | direct access to the darknet”
The sent-report ledger records the first outgoing report at .
The recorded recipient is compliance@tucows.com.
The latest stored availability evidence still shows the domain reachable; 2 months 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.
dark.direct returned HTTP status 200 in a check dated 2026-10-01, one of several dated source observations recorded for this domain. The same evidence set records a registration date of 2021-10-02 with Tucows Domains Inc. as registrar.
A PageSpeed check on 2026-08-11 recorded a performance score of 100 for dark.direct. VirusTotal, checked on 2026-09-25, reported 4 detections across 91 scanners. OTX, checked on 2026-08-21, listed 4 pulses. The domain was first observed on 2026-08-11, and the PhishDestroy internal listing is recorded as true. The IP address 172.67.181.150 is associated with AS13335 Cloudflare, Inc. in the US.
The named sources measure different things: an HTTP response code, a performance score, scanner detections, OTX pulses, and a publisher-owned catalogue entry. Because the checks carry separate dates, the records can be compared as a chronology without treating any single metric as a verdict. The PhishDestroy listing is the only catalogue entry in this evidence set, so it should be read as one publisher's record rather than a consensus.
For dark.direct, preserve the HTTP, PageSpeed, VirusTotal, OTX, and PhishDestroy records as separate dated artifacts. Compare the VirusTotal and OTX observations against later checks to see whether the recorded counts move. Review the PhishDestroy catalogue entry alongside the other source records rather than in isolation. Re-check the domain's HTTP response and performance score on a fresh date to extend the timeline.
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
For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.
Edge-IP reputation is not attributed to this domain.
aspen.ns.cloudflare.comsonny.ns.cloudflare.comLocation describes the IP network.
6e0e0498f8e5758e06897df97ca0c51aa2b148eeb12a60dcd5a93c9330af5446Saved 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 dark.direct · checked Aug 11, 2026
104.21.31.249. 12 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-20260811-B404BE Recipient: compliance@tucows.com Registrar: Tucows Domains Inc (Canada) Policy Violations: Participates in DNS Abuse Framework; explicitly recognizes phishing, malware, botnets, pharming, spam-as-vector as abuse requiring registrar action Applicable Laws: Criminal Code §342.1 (unauthorized access), §380 (fraud)
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