Scamadviser
1/100
Trust score, lower = worse
Open reportPhishDestroy records a review of blackops-tor-access.online detailing its claims to provide access to a darknet market and onion links.
Page title: “Black Ops Darknet | Onion URL, Tor-Zone & Mirrors 2026”
Use caution — do not enter credentials or personal information.
Risk score, higher = worse · How this score works
Pick what happened and tick the steps as you go. The ticks are kept only in this browser.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
URLScan capture · 2026-11-15 00:33 UTC · SHA-256 80a44aa9…9fd40b9
PhishDestroy analysis, reviewed version
On 2026-11-15, blackops-tor-access.online displayed a page titled Black Ops Darknet, featuring headings such as Tor-Zone Desk and Onion URL Bar. The page prominently lists a primary onion URL along with backup and mirror addresses, explicitly stating that login never runs on this clearnet portal. Additional sections detail market crypto options including XMR and BTC, alongside instructions for Tor browser access and a 2026 market guide.
The stored VirusTotal domain result reports 0 detections out of 92 engines.
1/100
Trust score, lower = worse
Open report4 community references
Open reportScan report
Open reportPage capture
SHA-256 50bd7145…cae1487
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
Narrative generation metadata
Open reportThe narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
Stored page, network and scanner observations, grouped by source and observation time.
| Mail configuration | Spf lookups: 0 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Crawler rules | Agents: *, Amazonbot, Applebot-Extended, Bytespider, CCBot; Present: ✓; Sitemaps: https://blackops-tor-access.online/sitemap.xml |
| Sitemap | Present: ✓; URL count: 7 |
| Page title and metadata | Ogurl: https://blackops-tor-access.online/; Title: Black Ops Darknet | Onion URL, Tor-Zone & Mirrors 2026; Author: Black Ops Darknet; Ogtype: website; Robots: index,follow,max-snippet:-1,max-image-preview:large,max-video-preview:-1; Ogimage: https://blackops-tor-access.online/img/og.jpg; Ogtitle: Black Ops Darknet | Onion URL, Tor-Zone & Mirrors 2026; Keywords: black ops darknet, blackops darknet, blackopsdarknet, black ops darknet tor-zone, blackops darknet marketplace 2026 guide, blackops market mirrors 2026 bar, black ops onion url, black ops market mirrors, black-ops-market, blackops-darknet, blackopsdarknet.com, blackopsz6mjifcszfjvptzosryokuehypbmme6; Ogsitename: Black Ops Darknet; Themecolor: #0c100b; Description: Black ops darknet 2026: verified onion URL ending in vhqd, tor-zone access, blackops market mirrors 2026 bar and marketplace guide. Not Call of Duty — Tor market only on blackops-tor-access.online.; Twittercard: Summary large image; Canonicalurl: https://blackops-tor-access.online/; Ogdescription: Black ops darknet 2026: verified onion URL ending in vhqd, tor-zone access, blackops market mirrors 2026 bar and marketplace guide. Not Call of Duty. |
| Trackers | Requests: 7; Trackers: (Name: Google Fonts; Company: Google; Country: US; Category: Hosting; Requests: 1) |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 0; Wait: 49; Download: 0; Response ms: 97 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 80, 443, 8080 |
| Carbon | Bytes: 22440; Co2 grams: 0.0008; Cleaner than: 54 |
| DNS server | NS: (IP: 162.159.38.143; Host: lilith.ns.cloudflare.com), (IP: 173.245.59.113; Host: fred.ns.cloudflare.com); Zone: blackops-tor-access.online |
| Location | IP: 2606:4700:3035::6815:203a; ASN: 13335; Org: Cloudflare, Inc.; City: Toronto; Country: CA |
| SSL | Issuer: Google Trust Services / WE1; Subject: blackops-tor-access.online |
| DNS records | A: 104.21.32.58, 172.67.184.56; NS: lilith.ns.cloudflare.com, fred.ns.cloudflare.com; Soa: Nsname: fred.ns.cloudflare.com; Hostmaster: dns.cloudflare.com; Serial: 2419743728; Refresh: 10000; Retry: 2400; Expire: 604800; Minttl: 1800; Txt: google-site-verification=hkJ4cvVOAt7Yox2qtyIUHu2rWtMcDLsPWSkwijdCt68; Aaaa: 2606:4700:3035::6815:203a, 2606:4700:3036::ac43:b838 |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: ✗; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Firewall | Waf: Cloudflare; Has waf: ✓ |
| Get IP | IP: 2606:4700:3036::ac43:b838; Family: 6 |
| Redirects | Chain: https://blackops-tor-access.online |
| Tech stack | Technologies: Priority Hints, Google Font API, Cloudflare, RSS, Open Graph, HTTP/3 |
| Page links | External: https://onion-wiki.com/, http://blackopsz6mjifcszfjvptzosryokuehypbmme66awxuet4en5n2vhqd.onion/, http://blackopsf7swtcswyaaj3xyqlchrggmmqjgp3ahxksqsz2g366uqfgid.onion/, http://blackops527cggb6ybayggx3bjt24xz32rotdugs6ikejxdlik6dyiid.onion/, https://onion-wiki.com/shops/blackops/; External count: 5; Internal count: 9 |
| Registration record | Registrar: TLD Registrar Solutions Ltd; Created: 2026-07-12T17:10:28Z; Updated: 2026-07-17T17:12:29Z; Expires: 2027-07-12T17:10:28Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: fred.ns.cloudflare.com, lilith.ns.cloudflare.com |
| HTTP headers | Headers: Server: cloudflare; Content type: text/html |
80a44aa9…9fd40b9 SHA-256 of the prepared copy given to the model: edf5a7ae…0e6004a 80a44aa9ebbb477862874f61601eacaa50bed2d9b8423dade63f163aa9fd40b9 · 170517 bytes 9a68e30e989ab6feb526e744f4b6d5d380001ed9e0fbecdb74dcd415eced2240 · 174046 bytes 5c1f81ece99835e7555e231efb6a28d37b893c533d7915b255a9972887ea0776 · 449522 bytes 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.
fred.ns.cloudflare.comlilith.ns.cloudflare.comnsname: fred.ns.cloudflare.comhostmaster: dns.cloudflare.comserial: 2419743728refresh: 10000retry: 2400expire: 604800minttl: 1800Location describes the IP network.
blackops-tor-access.online*.blackops-tor-access.onlineSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
The site was serving its pages at the latest check.
Google PageSpeed Insights — mobile performance audit of blackops-tor-access.online ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://blackops-tor-access.online/Content-Type: text/htmlServer: cloudflareCache-Control: max-age=300CF-Cache-Status: MISSContent-Encoding: gzip5d2498f113cf940d0dfbf70f571464873def4d116e40f2a7191b1da33545df53summary_large_imageh3=":443"; ma=86400max-age=300MISSa5aa2d5b2c025cc6-KEFkeep-alivegziptext/htmlSun, 15 Nov 2026 00:35:39 GMTThu, 29 Oct 2026 13:35:44 GMT{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=Cb4WAupNb%2FBU57Cpgd9OIiEzOgL8rtz0ALosNDMiNPhlm7IA5olOEE1hMxWGLGra2eLaQoJG0BN2iskocPTvaK5WAhAXOO06ZWUb6%2BZzhpGHXwWUtDWB1m0nTWncvSC4rtq2MZUlPSgcloudflarecfCacheStatus;desc="MISS"chunkedAccept-EncodingValues retained by the collector; long values may be shortened during collection.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 17 SHA-256 hashes: 17 URLScan scan:
Network requests that the URLScan browser recorded while loading the page. URLScan does not provide a hash for every request. PhishDestroy retrieved this list on 2026-11-15 00:37 UTC.
Open this scan on URLScan 01a1dc9f-8727-755f-bee5-b6ee8cc44385 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Serving page content
page content returned
Serving page content
page content returned
Serving page content
page content returned
Serving page content
page content returned
Serving page content
page content returned
Serving page content
page content returned
Serving page content
page content returned
Reachable
Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
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.
Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.
Download all records as JSON| ID | Stored data |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
blackops-tor-access.online Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.
The draft stays only with you.
First secure your money: call your bank or revoke wallet approvals. Immediate steps →
Emergency help from security researchers when a crypto wallet is being drained right now.
Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.
Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.
Forward scam emails and text messages to the National Cyber Security Centre, which takes down the malicious sites it finds.
Emailreport@phishing.gov.uk Text messages7726Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.
Forward phishing emails to the Anti-Phishing Working Group.
Emailreportphishing@apwg.orgNational Cyber Crime Reporting Portal. For financial fraud, also call the 1930 helpline straight away.
Helpline1930Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
blackops-tor-access.online)Even if you don't have all details — file a report anyway. Partial information still helps investigations.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
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
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.