The qshield.pro site operates a quantum threat scanner that prompts visitors to connect their cryptocurrency wallets to check for vulnerability against Shor's algorithm. Anyone who has interacted with the site or connected a wallet should immediately revoke any token approvals granted to unfamiliar contracts.
Page title: “QuantumShield | Protect Your Crypto Wallet from Quantum Attacks”
More about the sources
Recorded security signals
Listed by external blocklists: ScamSniffer. Use caution — do not enter credentials or personal information.
Expert view has every section: DNS, TLS, network requests, hashes and the raw JSON.
Analysis
Domain summary
PhishDestroy first recorded qshield.pro on 2026-11-22. Listed by external blocklists: ScamSniffer. Risk: critical (evidence score 100/100). Registrar: PDR. Status: Last known active. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.
URLScan capture · 2026-11-22 11:16 UTC · SHA-256 439ffe54…b77552d
PhishDestroy analysis, reviewed version
QuantumShield landing page layout and claims
The qshield.pro landing page brands itself as "QuantumShield" and displays a warning that "Your crypto wallet is vulnerable to quantum computers." The layout includes prominent "Scan My Wallet" and "Connect Wallet" buttons alongside a "Vulnerability Scanner" widget that invites users to connect their assets across networks. Below the main headline, the interface shows statistics like "105 Google Willow Qubits", "5-7 yrs until ECDSA breaks", "$2.1T crypto at risk", and "73% wallets exposed." Further down, it lists "Supported Networks" such as EVM, Tron, XRP Ledger, and Solana, and references technical concepts like Shor's algorithm and ECDSA secp256k1. The page uses these technical details to create urgency around hypothetical quantum computing threats while encouraging visitors to interact with its scanning widget.
Security findings and borrowed brand mentions
ScamSniffer blocks it, so it is not a trusted tool. Furthermore, Arbitrum, Ethereum, Ledger, Solana and TRON appear across the interface and page code, which served to lend technical credibility to an unknown platform where nothing indicates any actual partnership with these blockchain projects. The domain was registered on 26 Jun 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com, and it sits behind Cloudflare, which hides the real server.
What happens if you connect a wallet
Pages that invite users to connect crypto wallets to check for advanced threats typically present malicious signature requests once a wallet is linked. Because the site borrows recognized blockchain names to appear legitimate, visitors may trust the interface and inadvertently authorize harmful transactions.
Recommended actions for visitors
Visitors who have already connected their wallets to qshield.pro should immediately open their wallet settings, inspect active connections, and revoke any unfamiliar token approvals or permissions. It is crucial to monitor account balances and transfer remaining funds to a secure, newly generated wallet if unauthorized access is suspected. Always verify the authenticity of security tools before linking any cryptocurrency assets.
Source evidence4 sources
SourceResultRecorded · UTCOpen
Cloudflare Radar
Scan report
Open report Cloudflare RadarOriginal source recordObserved: 12 fields
Open report Page code check by a separate monitor · 100 / 100 · 2026-11-22 11:20 UTC
This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.
Heuristic score
100
Analyzed at
2026-11-22T11:20:11Z
Source timestamp
2026-11-22 12:20:11
Technical metadata
PhishDestroy narrative
Narrative generation metadata
Open report Title, description and generation record
The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.
AI title
qshield.pro — QuantumShield vulnerability portal
AI description
qshield.pro presents a quantum wallet scanner requesting wallet connections for security checks, flagged by ScamSniffer. Avoid linking assets.
AI summary
QuantumShield landing page layout and claims The qshield.pro landing page brands itself as "QuantumShield" and displays a warning that "Your crypto wallet is vulnerable to quantum computers." The layout includes prominent "Scan My Wallet" and "Connect Wallet" buttons alongside a "Vulnerability Scanner" widget that invites users to connect their assets across networks. Below the main headline, the interface shows statistics like "105 Google Willow Qubits", "5-7 yrs until ECDSA breaks", "$2.1T crypto at risk", and "73% wallets exposed." Further down, it lists "Supported Networks" such as EVM, Tron, XRP Ledger, and Solana, and references technical concepts like Shor's algorithm and ECDSA secp256k1. The page uses these technical details to create urgency around hypothetical quantum computing threats while encouraging visitors to interact with its scanning widget. Security findings and borrowed brand mentions ScamSniffer blocks it, so it is not a trusted tool. Furthermore, Arbitrum, Ethereum, Ledger, Solana and TRON appear across the interface and page code, which served to lend technical credibility to an unknown platform where nothing indicates any actual partnership with these blockchain projects. The domain was registered on 26 Jun 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com, and it sits behind Cloudflare, which hides the real server. What happens if you connect a wallet Pages that invite users to connect crypto wallets to check for advanced threats typically present malicious signature requests once a wallet is linked. Because the site borrows recognized blockchain names to appear legitimate, visitors may trust the interface and inadvertently authorize harmful transactions. Recommended actions for visitors Visitors who have already connected their wallets to qshield.pro should immediately open their wallet settings, inspect active connections, and revoke any unfamiliar token approvals or permissions. It is crucial to monitor account balances and transfer remaining funds to a secure, newly generated wallet if unauthorized access is suspected. Always verify the authenticity of security tools before linking any cryptocurrency assets.
ScamSniffer blocks it, so it is not a trusted security scanner. Independent blocklists flag the domain because it attempts to interact with visitor wallets under false pretenses.
What happens if I connected my wallet on qshield.pro?
Connecting your wallet to an untrusted site can expose you to malicious signature requests that grant unauthorized access to your funds. You should immediately open your wallet settings, check for active connections, and revoke any unfamiliar token approvals.
Why does qshield.pro mention Ethereum and Solana?
The site lists prominent networks like Arbitrum, Ethereum, Ledger, Solana and TRON to create a false sense of authority and familiarity. Mentioning these blockchains does not mean the platform has any official relationship with them.
Edge-IP reputation is not attributed to this domain.
Nameservers 2
bart.ns.cloudflare.com
sureena.ns.cloudflare.com
SOA
nsname: bart.ns.cloudflare.com
hostmaster: dns.cloudflare.com
serial: 2418592984
refresh: 10000
retry: 2400
expire: 604800
minttl: 1800
Location describes the IP network.
TLS certificate
Issuer
WE1
Valid from
2026-10-22 23:35:35
Valid until
2027-01-21 00:33:10
Hostname match
Yes
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0b34159f650a88452dc33703fac5a5f4e5b345e7a1d0cdd021a0c7db10f7d58aCertificate names · 2 SANs
qshield.pro
*.qshield.pro
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
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-22 11:18 UTC.
Loads saved data; the suspicious site is not opened.
Captured network requests
#
Network request
HTTP method · status
Type
Uncompressed size
Response body SHA-256
Stored observation history1
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Domain monitor · First collection record
Reachable
All retained availability observations2
Source: availability monitor. Every retained observation remains separate, including records with the same date or evidence hash but different sources or DNS states. An unknown state is not proof that the site is offline.
Recorded events: 9. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
The domain remains reachable or access-restricted; future checks may update this observation.
ongoing
Recorded activity
4 entries
Lifecycle
Domain registered
Added to PhishDestroy+148 d 22 h
Wayback Machine
Page archived
same minute
Cloudflare Radar
Phishing
+2 min
Added to PhishDestroy
qshield.pro
same minute
URLScan
Page captured
How we investigate & report
Public scans, evidence and abuse channels
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.
01Public scans & evidence collection10 sources and tool groups
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
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.
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
Report all
A similar name alone does not prove fraud. Send the list to services that check each address themselves. Report a domain as phishing only if you saw a fake page on it.
xn--ledgr-9za.comLookalike lettersVariant of ledger.comInternal reportNS ns-cloud-d1.googledomains.comledgerk.comAdded characterVariant of ledger.comInternal reportA 156.250.67.229NS ns1.bdydns.cnopltimism.ioInserted characterVariant of optimism.ioNS ns1.domaindiscount24.netoptimi.sm.ioSplit into subdomainVariant of optimism.ioA 3.139.159.151optimis.ioMissing characterVariant of optimism.ioA 51.91.236.193MX alt1.aspmx.l.google.comNS dns104.ovh.netoptimise.ioBit flipVariant of optimism.ioA 13.248.169.48NS ns3.afternic.comoptimisrn.ioLookalike lettersVariant of optimism.ioNS 1-ceci.njalla.dooptimizm.ioReplaced characterVariant of optimism.ioA 104.21.21.200NS grace.ns.cloudflare.comoptimjsm.ioReplaced characterVariant of optimism.ioNS 1-ceci.njalla.dooptimlsm.ioLookalike lettersVariant of optimism.ioNS 1-ceci.njalla.dooptimusm.ioReplaced characterVariant of optimism.ioA 188.114.96.3NS autumn.ns.cloudflare.comoptirnism.ioLookalike lettersVariant of optimism.ioA 104.21.75.127NS mario.ns.cloudflare.comoptirnlsm.ioLookalike lettersVariant of optimism.ioA 104.21.77.113NS mario.ns.cloudflare.comoptomism.ioReplaced characterVariant of optimism.ioA 34.42.100.71NS ns-cloud-e1.googledomains.coma.rbitrum.ioSplit into subdomainVariant of arbitrum.ioA 188.114.96.3abitrum.ioMissing characterVariant of arbitrum.ioA 188.114.96.3NS hank.ns.cloudflare.comabritrum.ioSwapped charactersVariant of arbitrum.ioA 188.114.96.3NS hank.ns.cloudflare.comarbbitrum.ioRepeated characterVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netarbiitrum.ioRepeated characterVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netarbirtum.ioSwapped charactersVariant of arbitrum.ioA 188.114.96.3NS hank.ns.cloudflare.comarbirum.ioMissing characterVariant of arbitrum.ioA 199.91.220.73NS ns1.dnsowl.comarbit.rum.ioSplit into subdomainVariant of arbitrum.ioA 13.248.169.48NS ns1.afternic.comarbitr.um.ioSplit into subdomainVariant of arbitrum.ioA 3.139.159.151arbitram.ioVowel swapVariant of arbitrum.ioA 77.247.179.86NS ns1.badgerdns.comarbitrium.ioInserted characterVariant of arbitrum.ioA 88.212.204.58MX mx.yandex.netNS c.ns.over.ruarbitrm.ioMissing characterVariant of arbitrum.ioA 104.21.28.233NS hank.ns.cloudflare.comarbitrmu.ioSwapped charactersVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netarbitru.ioMissing characterVariant of arbitrum.ioA 104.21.2.146NS hank.ns.cloudflare.comarbitruum.ioRepeated characterVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netarbittrum.ioInserted characterVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netarbitum.ioMissing characterVariant of arbitrum.ioA 104.21.95.219NS hank.ns.cloudflare.comarbiturm.ioSwapped charactersVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netarbtirum.ioSwapped charactersVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netarbtrum.ioMissing characterVariant of arbitrum.ioA 188.114.96.3NS hank.ns.cloudflare.comaribtrum.ioSwapped charactersVariant of arbitrum.ioA 199.91.220.73NS ns1.dnsowl.comaritrum.ioMissing characterVariant of arbitrum.ioA 188.114.96.3NS hank.ns.cloudflare.comrabitrum.ioSwapped charactersVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netrbitrum.ioMissing characterVariant of arbitrum.ioA 188.114.96.3NS hank.ns.cloudflare.comarbitrrum.ioInserted characterVariant of arbitrum.ioA 104.21.56.168NS hank.ns.cloudflare.comarbitrumm.ioAdded characterVariant of arbitrum.ioA 185.53.179.128NS ns1.dyna-ns.netarbitrun.ioLookalike lettersVariant of arbitrum.ioA 104.21.88.223NS hank.ns.cloudflare.comxn--rbitrum-r3a.ioLookalike lettersVariant of arbitrum.ioA 104.21.60.23NS dalary.ns.cloudflare.comathereum.orgBit flipVariant of ethereum.orgA 199.188.200.6MX mail.athereum.orgNS dns1.namecheaphosting.comdethereum.orgInserted characterVariant of ethereum.orgA 216.198.79.1NS liv.ns.cloudflare.come.thereum.orgSplit into subdomainVariant of ethereum.orgA 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.comefhereum.orgReplaced characterVariant of ethereum.orgA 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.comehereum.orgMissing characterVariant of ethereum.orgA 15.197.225.128NS ns65.domaincontrol.cometereum.orgMissing characterVariant of ethereum.orgA !ServFailNS !ServFaileth3reum.orgReplaced characterVariant of ethereum.orgA 15.197.142.173NS ns31.domaincontrol.comether.eum.orgSplit into subdomainVariant of ethereum.orgA 13.248.169.48NS ns1.afternic.cometheream.orgVowel swapVariant of ethereum.orgA 162.255.119.154MX eforward1.registrar-servers.comNS dns1.registrar-servers.comethereim.orgReplaced characterVariant of ethereum.orgA 15.197.142.173NS ns33.domaincontrol.comethereium.orgInserted characterVariant of ethereum.orgA 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.cometherem.orgMissing characterVariant of ethereum.orgA 15.197.225.128NS ns39.domaincontrol.cometheremu.orgSwapped charactersVariant of ethereum.orgA 13.248.169.48NS ns1.afternic.comethereom.orgVowel swapVariant of ethereum.orgA 192.0.78.24NS ns1.wordpress.cometheresum.orgInserted characterVariant of ethereum.orgA 104.21.87.66NS aron.ns.cloudflare.comethereujm.orgInserted characterVariant of ethereum.orgA 104.21.46.240NS jerry.ns.cloudflare.comethereum2.orgAdded characterVariant of ethereum.orgA 24.199.74.33NS ns3.namefi.ioethereum3.orgAdded characterVariant of ethereum.orgNS a.share-dns.comethereum4.orgAdded characterVariant of ethereum.orgA 198.54.117.242NS failed-whois-verification.namecheap.comethereumc.orgAdded characterVariant of ethereum.orgA 188.114.96.3NS camilo.ns.cloudflare.comethereumd.orgAdded characterVariant of ethereum.orgA 188.114.96.3NS earl.ns.cloudflare.comethereumorg.comVariantVariant of ethereum.orgNS ns1.openprovider.nlethereumr.orgAdded characterVariant of ethereum.orgA 188.114.96.3NS monroe.ns.cloudflare.comethereums.orgAdded characterVariant of ethereum.orgA 15.197.148.33MX mailstore1.secureserver.netNS ns73.domaincontrol.comethereumx.orgAdded characterVariant of ethereum.orgA 64.190.63.222MX localhostNS ns1.sedoparking.comethereun.orgLookalike lettersVariant of ethereum.orgA 52.20.84.62NS ns1.squadhelp.comethereunm.orgLookalike lettersVariant of ethereum.orgA 104.21.86.145NS koa.ns.cloudflare.comethereurm.orgLookalike lettersVariant of ethereum.orgA 188.114.96.3NS rita.ns.cloudflare.comethereurn.orgLookalike lettersVariant of ethereum.orgMX eforward1.registrar-servers.comNS dns1.registrar-servers.comethereuym.orgInserted characterVariant of ethereum.orgA 104.21.22.142NS everton.ns.cloudflare.comethereuzm.orgInserted characterVariant of ethereum.orgA 188.114.96.3NS dale.ns.cloudflare.comethereyum.orgInserted characterVariant of ethereum.orgA 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.cometherium.orgVowel swapVariant of ethereum.orgA 32.216.8.188NS ns1.no-ip.cometherrum.orgReplaced characterVariant of ethereum.orgMX eforward1.registrar-servers.comNS dns1.registrar-servers.cometherteum.orgInserted characterVariant of ethereum.orgA 13.248.243.5NS ns41.domaincontrol.cometherum.orgMissing characterVariant of ethereum.orgA 103.224.212.201MX park-mx.above.comNS ns1.abovedomains.comethezeum.orgBit flipVariant of ethereum.orgA 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.comethireum.orgVowel swapVariant of ethereum.orgA 192.64.119.29MX eforward1.registrar-servers.comNS dns1.registrar-servers.comethnereum.orgInserted characterVariant of ethereum.orgA 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.comethreum.orgMissing characterVariant of ethereum.orgA 15.197.225.128NS ns65.domaincontrol.comethureum.orgBit flipVariant of ethereum.orgA 162.255.119.109MX eforward1.registrar-servers.comNS dns1.registrar-servers.cometihereum.orgLookalike lettersVariant of ethereum.orgA 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.comithereum.orgVowel swapVariant of ethereum.orgA 188.114.96.3NS celine.ns.cloudflare.comothereum.orgVowel swapVariant of ethereum.orgNS ns-cloud-a1.googledomains.comrethereum.orgInserted characterVariant of ethereum.orgA 54.36.108.60MX eforward1.registrar-servers.comNS dns1.registrar-servers.comsethereum.orgInserted characterVariant of ethereum.orgA !ServFailNS !ServFail
Showing 100 of 371
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Same registrar: PDR6
Registered through the same registrar. A registrar serves millions of unrelated customers, so this groups reports rather than proving a link.
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Secure your accounts and funds first, then report. If credentials were compromised, report immediately. Do not engage with recovery scammers.
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.
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Entered a password — change it on that service and on every other site where you used the same password
Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website
Downloaded a file — do not open it and scan the device with security software
Shared a seed phrase or private key — move the remaining funds to a new wallet with a new seed phrase; the exposed wallet is no longer safe
Connected a wallet but signed nothing — disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds
Approved token spending (approve / permit) — revoke that approval with a token-approval checker (revoke.cash)
Sent crypto — save the transaction hash, your address and the receiving address; blockchain transactions cannot be reversed
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including qshield.pro)
Communications — emails, texts, phone numbers, usernames the scammer used
Even if you don't have all details — file a report anyway. Partial information still helps investigations.
Where should I report the scam?
FBI IC3 — Internet Crime Complaint Center (US federal reporting)
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
Local police — creates an official record, even if they can't act immediately
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
How do phishing scams typically work?
Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect
How can I protect myself in the future?
Bookmark official sites — never click links from emails, DMs, or ads
Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
"Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines
Beware of recovery scammers! Recovery scammers may pose as investigators, lawyers, or tracing services. Do not pay upfront fees or disclose credentials.Learn more about recovery fraud →
About this reportSources, observation dates and corrections
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.