Skip to content

pgp-verified · updated 21 apr 2026

Drughub verified urls

Every drughub market link on this page was confirmed against a PGP-signed announcement from the Drughub team within the last forty-eight hours. No affiliate redirects. No unverified scraped addresses. You get the real onion address, the current mirror, and the exact timestamp of the last check.

Phishing sites use drughub's interface as a template. The copies look identical. The only reliable difference is the onion address itself — and the only reliable source for the correct address is a PGP-signed announcement. That is all this page does.

2 verified links
48h check cycle
99.1% primary uptime
Access manual
Drughub marketplace interface screenshot showing the Monero-only darknet market homepage

The Drughub marketplace front page as it appears in Tor Browser. The PGP fingerprint in the lower-right footer is the primary authenticity check — compare it against the team's long-lived signing key before entering any credentials.



how to stay safe

Verifying a drughub link yourself

You do not need to trust this directory. Every step below produces an independently verifiable result using only public tools. The verification chain is external to this portal by design.

  1. Find the PGP-signed announcement on Dread

    Open Tor Browser and navigate to the Drughub subforum on Dread. Look for the most recent mirror announcement pinned by the market admins. Every legitimate drughub url update comes with a PGP signature block attached to the post. Unsigned announcements should be treated as unverified regardless of how official they appear.

    Copy the full PGP-signed message including the signature block. You will need it in step two.

  2. Verify the signature with GnuPG

    Install GnuPG if you have not already. Import the Drughub team's public key — the fingerprint is published on their Dread profile and has not changed since August 2023. Then verify the announcement you copied:

    # Import the Drughub team's PGP key
    gpg --import drughub-team-pubkey.asc
    
    # Verify the signed announcement
    gpg --verify drughub-announcement.txt.asc drughub-announcement.txt
    
    # Expected: "Good signature from Drughub Team"
    # Key fingerprint: compare against the one on their Dread profile

    If the verification returns anything other than a good signature, do not use the addresses in that announcement. A bad signature means the message was modified after signing, or was never signed by the real key.

  3. Load the address in Tor Browser and check the footer

    Paste the verified onion address into Tor Browser. Once the Drughub marketplace loads, scroll to the page footer. Every legitimate drughub deployment includes a short PGP fingerprint in the footer matching the team's signing key. If that fingerprint is absent, different, or illegible, do not proceed.

    This step catches phishing servers that replicated the Drughub interface. A phishing server cannot produce the correct footer fingerprint without the team's private key. It is the most reliable single anti-phishing check available.

  4. Compare first and last six characters of the address

    After pasting the address into Tor Browser's URL bar, visually compare the first six and last six characters of what you pasted against what appears in the address bar. Phishing operators build vanity addresses that match the first several characters of the real address. The last six characters are a cryptographic checksum derived from the server's key — they are what you are really checking. A match on the first characters only is not sufficient. Both ends must match exactly.

GnuPG terminal showing a valid PGP signature verification for a Drughub announcement

GnuPG signature verification of a Drughub team announcement. "Good signature" with matching fingerprint means the address in the announcement is authentic.

"One wrong character sends a Monero payment to a server that is not drughub. The check takes ninety seconds. The mistake is irreversible."

— From the Drughub access manual

drughub mirror links

Why Drughub runs multiple onion addresses

Three reasons the same drughub market operates under multiple onion addresses simultaneously. Understanding them helps you use mirrors correctly, not as a fallback of last resort.

01

DDoS resilience

Darknet marketplaces are constant targets for distributed denial-of-service attacks — from competitors, extortion rings, and researchers probing infrastructure. When a primary drughub link is saturated, traffic routes to a mirror on a separate server with a fresh Tor circuit pool. The marketplace stays reachable. The same attack hits one address, not both simultaneously. Bookmarking the mirror is insurance, not paranoia.

02

Planned server migration

Drughub migrated servers in 2024 as part of post-acquisition infrastructure consolidation after absorbing SuperMarket. Mirror addresses allow a zero-downtime transition — the new server goes live as a mirror first, traffic gradually shifts, and the old address is deprecated after the migration confirms stable. Users who bookmarked the old drughub link see a redirect notice pointing to the new primary. The portal history page covers the 2024 migration in detail.

03

Operational security rotation

Rotating onion addresses periodically is standard darknet operational security. A long-lived address accumulates more targeting data — traffic analysis attempts, relay correlation attacks, infrastructure fingerprinting. Periodic rotation resets this. The Drughub team announces each rotation on Dread with a PGP signature, giving users a verified path to the new drughub market url without relying on clearnet search results. The rotation cadence is irregular by design — predictable rotation schedules are exploitable.

Drughub interface showing the mirror navigation and address display in Tor Browser
The Drughub marketplace interface as seen in Tor Browser. Notice the absence of JavaScript-dependent elements — the market renders fully with JS disabled, which is the recommended Tor Browser security setting.

source comparison

Where to get a drughub link — and where not to

Not all sources for drughub onion links are equal. The table below covers the four most common types. The differences in PGP verification and update frequency are not minor — they determine whether you land on the real market or a phishing clone.

Source type PGP verified Update frequency Affiliate/redirect Phishing risk
drughubportal.live Every 48 hours Each verification cycle None Screened
Dread forum thread (official) PGP-signed by team On rotation only None Low (with key check)
Ad-supported link directories Rarely Irregular, often stale Common High
Clearnet search results Never Not applicable Common Very high

The official Dread thread is the primary source — this directory monitors it and republishes verified addresses with timestamps. Using this directory is not a shortcut around Dread; it is a pre-checked snapshot of Dread's verified output, with the three-step verification already completed for you.

Drughub primary vs. mirror — what differs

Property Primary link Mirror link
Onion address drughub75…ad.onion rughubrwg…id.onion
Marketplace content Identical Identical
Account access Same account on both Same account on both
Order visibility Full order history Full order history
Response time ~9 sec (Tor avg) ~12 sec (Tor avg)
DDoS priority Primary target Secondary (lower traffic)

before you connect

Security practices for using drughub links

Getting the correct drughub market link is necessary. Using it safely is a separate step. These nine practices cover the technical baseline. None of them require advanced knowledge — only consistent habits.

  • Use only Tor Browser Regular browsers cannot reach .onion addresses. A VPN alone does not substitute for Tor. Download Tor Browser from torproject.org only — every other source has distributed malware at some point.
  • Set security to Safest Tor Browser's Security Level → Safest disables JavaScript globally. Drughub renders without JS. Enabling JS expands your attack surface without adding any functionality.
  • Never resize Tor Browser Maximizing the browser window creates a fingerprint based on your screen resolution. Keep Tor Browser at its default window size.
  • Pay from a self-custody wallet Drughub only accepts Monero. Paying from an exchange wallet ties the transaction to your identity. Use Feather Wallet or Cake Wallet — wallets you control.
  • Consider Tails OS For higher-threat use cases, run Tor Browser inside Tails from a USB stick. Tails leaves no trace on the host machine and routes all traffic through Tor by default.
  • Store your PGP key properly Your drughub account is tied to a PGP key. Keep the private key on a dedicated device in cold storage. KeePassXC handles encrypted key storage well. Cloud backups of private keys negate their purpose.
  • Do not reuse identities A username or email used anywhere on the clearnet should not appear on drughub. Separate personas, separate keys, separate devices when threat level warrants it.
  • Use GnuPG for all messages All vendor communication on drughub should be PGP-encrypted regardless of whether the platform enforces it in a given message thread. Plaintext messages are a liability.
  • Read Privacy Guides The Privacy Guides project maintains current, non-commercial recommendations for operational security. One afternoon with that resource is the highest-leverage preparation available before a first drughub visit.

Questions about drughub urls and mirrors

Nine common questions. Direct answers without padding. The full getting-started walkthrough is on the manual page.


The verified drughub link is above.

Copy it, paste it into Tor Browser, check the footer fingerprint. That is the complete process. The access manual covers everything else.

Loading…
Read access manual
  • Open only in Tor Browser. Regular browsers cannot resolve .onion domains.
  • Pay with Monero (XMR) from a self-custody wallet, not an exchange.
  • Check the PGP fingerprint in the footer when the page loads — it must match the team's key.