URLQuery
2 det.
Open reportPhishDestroy records the prime-onion.click page displaying multiple onion service links and directory mirrors.
Page title: “Prime Onion {Access} 2026-11-14 23:50:05”
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.
The sent-report ledger records the first outgoing report at . The recorded recipient is abuse@server-panel.net. The latest stored availability evidence still shows the domain reachable; 6 days 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.
URLScan capture · 2026-11-14 23:40 UTC · SHA-256 1f954968…49d28e2
PhishDestroy analysis, reviewed version
The prime-onion.click page displays a Prime-branded archive interface featuring a top banner and navigation links for accessing an online marketplace. Below the header, the page presents multiple boxed sections containing listed onion v3 links, handshake latency metrics, and verification labels intended to direct users toward alternative network locations. Interactions are limited to viewing the listed mirror links and browsing the navigational menu options.
The stored VirusTotal domain result reports 0 detections out of 92 engines.
2 det.
Open report4 community references
Open reportScan report
Open reportPage capture
SHA-256 558d8063…5e01a15
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
65 / 100 · heuristic score · 5 brand references · 0 classifications
Content heuristic only; not the final score
Open reportThis dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
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 | MX: prime-onion.click; Spf: v=spf1 +a +mx +ip4:45.147.197.100 ~all; Dkim: default; Dmarc: ✓; Dkim bits: 2048; Spf lookups: 2 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Crawler rules | Agents: *; Present: ✓; Sitemaps: https://prime-onion.click/sitemap.xml |
| Sitemap | Present: ✓; URL count: 1 |
| Page title and metadata | Ogurl: https://prime-onion.click; Title: Prime Onion {Access} 2026-11-14 23:57:22; Ogtype: website; Robots: index, follow; Ogimage: https://prime-onion.click/prime-preview.jpg; Ogtitle: prime market link official · prime darknet market 2026; Keywords: prime market link, prime darknet market, prime marketplace, prime onion, prime official, prime verified, prime 2026; Description: Access the only official prime market link repository. prime darknet market, prime marketplace and prime onion addresses updated daily. prime verified mirrors with 2-4% commission, XMR/BTC, since March 2025.; Twittercard: Summary large image; Canonicalurl: https://prime-onion.click; Ogdescription: Verified prime market link repository. Access prime darknet market, prime marketplace, prime onion mirrors. Updated hourly with prime official validation. |
| Trackers | Requests: 3 |
| Forms and mixed content | Upgrade insecure: ✓; Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 0; Wait: 926; Download: 0; Response ms: 6091 |
| TLS connection | Alpn: h2; Cipher: TLS_AES_128_GCM_SHA256; Protocol: TLSv1.3; Versions: TLSv1, TLSv1.1, TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 21, 22, 53, 80, 110, 143, 443, 587, 993, 995 |
| Carbon | Bytes: 43571; Co2 grams: 0.0016; Cleaner than: 40 |
| DNS server | NS: (IP: 51.38.146.91; Host: ns3.zomro.com), (IP: 116.202.0.200; Host: ns4.zomro.su), (IP: 212.8.245.252; Host: ns1.zomro.net), (IP: 185.82.216.129; Host: ns2.zomro.ru); Zone: prime-onion.click |
| Cookies | Cookies: (Name: __ddg8_), (Name: __ddg10_), (Name: __ddg9_), (Name: __ddg1_; HTTP only: ✓), (Name: PHPSESSID; Session: ✓) |
| Location | IP: 45.147.197.100; ASN: 204601; Org: Zomro B.V.; City: Meppel; Country: NL |
| SSL | Issuer: Let's Encrypt / YR1; Subject: prime-onion.click |
| DNS records | A: 45.147.197.100; MX: Exchange: prime-onion.click; Priority: 0; NS: ns3.zomro.com, ns4.zomro.su, ns1.zomro.net, ns2.zomro.ru; Soa: Nsname: ns1.zomro.net; Hostmaster: mon.zomro.org; Serial: 2026031005; Refresh: 3600; Retry: 1800; Expire: 1209600; Minttl: 86400; Txt: v=spf1 +a +mx +ip4:45.147.197.100 ~all |
| Dnssec | Ds: ✗; Rrsig: ✗; Dnskey: ✗ |
| Hsts | Message: Site does not serve any HSTS headers. |
| HTTP security policies | Xframeoptions: ✗; Referrerpolicy: ✗; Xxssprotection: ✗; Permissionspolicy: ✗; Xcontenttypeoptions: ✗; Contentsecuritypolicy: upgrade-insecure-requests;; Stricttransportpolicy: ✗; Crossoriginopenerpolicy: ✗; Crossoriginembedderpolicy: ✗; Crossoriginresourcepolicy: ✗ |
| Firewall | Waf: DDoS-Guard WAF; Has waf: ✓ |
| Get IP | IP: 45.147.197.100; Family: 4 |
| Redirects | Chain: https://prime-onion.click |
| Page links | Internal count: 6 |
| Registration record | Registrar: Dynadot, LLC; Created: 2026-03-10T17:42:17Z; Updated: 2026-03-15T17:45:04Z; Expires: 2027-03-10T17:42:17Z; Status: clientTransferProhibited https://icann.org/epp; Nameservers: ns3.zomro.com, ns4.zomro.su, ns1.zomro.net, ns2.zomro.ru |
| HTTP headers | Headers: Server: ddos-guard; Content type: text/html; charset=UTF-8; X powered by: PHP/8.2.35; Content security policy: upgrade-insecure-requests; |
1f954968…49d28e2 SHA-256 of the prepared copy given to the model: f04804a0…57acd90 1f954968d582fd2e7e8d1781fab187d8edc7006b1b58021625dd3796d49d28e2 · 83909 bytes 1f954968d582fd2e7e8d1781fab187d8edc7006b1b58021625dd3796d49d28e2 · 83909 bytes 6b1813cacf0b5765678d4e93775f7515b0bd3cdd1a11115e4694413df6495000 · 87994 bytes 424d391bc780d0b7da7f470c2a8f4f0ca098ad12bbeaf3a524b27219a3be73aa · 90485 bytes f50ee37c56fe2a4d746f1ad96af46a55df666e5f1b1f14b2b9105f9e18b1f06d · 116581 bytes 686a5210ecfc4c5eab472f59a452404adb15dc4abc519847fa55707065355a44 · 125663 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.
ns1.zomro.netns2.zomro.runs3.zomro.comns4.zomro.sunsname: ns1.zomro.nethostmaster: mon.zomro.orgserial: 2026031005refresh: 3600retry: 1800expire: 1209600minttl: 86400prime-onion.clickpriority 0Location describes the IP network.
c3e5c4b436f4ec4ae2cf71004e86729779e46c165fd0dcd2c1b9f48bd880d547prime-onion.clickSaved 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.
Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.
cpanel.prime-onion.clickDomain recordftp.prime-onion.clickDomain recordmail.prime-onion.clickDomain recordwebmail.prime-onion.clickDomain recordwhm.prime-onion.clickDomain recordwww.prime-onion.clickDomain recordGoogle PageSpeed Insights — mobile performance audit of prime-onion.click ·
Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.
https://prime-onion.click/Server: ddos-guardContent-Type: text/html; charset=UTF-8X-Powered-By: PHP/8.2.35Cache-Control: no-store, no-cache, must-revalidateContent-Encoding: gzip4b160c1f3431c2ad3a5b56ada2be9f55915b62b4bbcf0271856ef1bc14728119summary_large_imageno-store, no-cache, must-revalidatekeep-alivegzipupgrade-insecure-requests;text/html; charset=UTF-8Sat, 14 Nov 2026 23:43:10 GMTThu, 19 Nov 1981 08:52:00 GMTtimeout=60no-cacheddos-guardchunkedAccept-EncodingPHP/8.2.35Values 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: 4 SHA-256 hashes: 4 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 19:13 UTC.
Open this scan on URLScan 01a1e09e-eab9-718c-8b20-c74c6fd60a31 ↗
Loads saved data; the suspicious site is not opened.
| # | Network request | HTTP method · status | Type | Uncompressed size | Response body SHA-256 |
|---|
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
Our scanner could not complete this check.
prime-onion.click 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
Reachable
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Lifecycle
Reported 250 d 1 h after registration
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 |
|---|
PD-4D43BA2A0DC087182CC1 Recipient: abuse@server-panel.net 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 ↗
prime-onion.click)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.