Cloudflare Radar
Scan report
Open reportthorchain.exchange copies a cross-chain swap platform layout with multiple brand names, registered via PDR Ltd. d/b/a PublicDomainRegistry.com.
Page title: “THORChain Swap | Cross-Chain BTC, ETH & Crypto Swaps”
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-20 03:39 UTC · SHA-256 2f45ced6…7e71618
PhishDestroy analysis, reviewed version
The page at thorchain.exchange opens with a clean, light-themed crypto trading interface featuring a prominent Thorchain logo in the top left corner. The central card displays a "Swap" and "Limit" toggle with input fields marked "Sell" and "Buy", showing currency selectors for BTC and ETH alongside live-looking market valuations and a bright green "Swap" button. The top navigation bar includes language selection buttons, a settings icon, and a "Wallet" connection button. In the footer, small text links provide standard pages such as "Privacy Policy", "Terms of Use", "Risk Policy", and links to report bugs or join a Discord server. The overall layout mimics a standard decentralized exchange liquidity pool or cross-chain token swap utility, designed to encourage users to connect an external web3 wallet.
Because the domain was registered on 7 Jul 2026 through PDR Ltd. d/b/a PublicDomainRegistry.com, it lacks a long-standing operational history. Furthermore, 1 other reported domain resolves to the same IP address and 152 use the same nameserver pair, pointing to a shared hosting pattern where the neighbour thorchan.org presents "THORChain Swap | Cross-Chain BTC, ETH & Crypto Swaps".
Under the hood, the underlying code incorporates references to several established ecosystems, specifically Arbitrum, Ethereum, Keplr, Ledger, MetaMask and OKX. Because these brand names appear without formal verification or partnership proof, they serve to establish unearned familiarity for visitors navigating the exchange interface.
Scan report
Open report76/100
Trust score, lower = worse
Open reportPage capture
SHA-256 db30a059…83e1871
Separate stored monitor snapshot; does not replace the primary report record or establish current availability.
100 / 100 · heuristic score · 14 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 | Spf lookups: 0 |
|---|---|
| Protective DNS results | Resolvers: 12; Blocked count: 0 |
| Web archive observations | Last: 2026-11-20T03:40:44Z; First: 2026-11-20T03:40:44Z; Changes: 0; Days archived: 1; Avg page bytes: 23342 |
| Page title and metadata | Ogurl: https://swap.thorchain.org; Title: THORChain Swap | Cross-Chain BTC, ETH & Crypto Swaps; Ogtype: website; Ogimage: https://swap.thorchain.org/og-image.png; Ogtitle: THORChain Swap | Cross-Chain BTC, ETH & Crypto Swaps; Ogsitename: THORChain Swap; Twittercard: Summary large image; Ogdescription: Swap Bitcoin to Ethereum and other cryptocurrencies instantly with THORChain. Native BTC swaps with no bridges, wrapping, or centralized exchanges. |
| Trackers | Requests: 5 |
| Forms and mixed content | Third party scripts: 0 |
| Status | Up: ✓; Code: 200; Timings: DNS: 0; Wait: 196; Download: 366; Response ms: 939 |
| TLS connection | Alpn: http/1.1; Cipher: TLS_AES_256_GCM_SHA384; Protocol: TLSv1.3; Versions: TLSv1.2, TLSv1.3; Authorized: ✓; Forward secrecy: ✓ |
| Ports | Open: 21, 22, 53, 80, 110, 143, 443, 587, 993, 995, 3306 |
| Carbon | Bytes: 77871; Co2 grams: 0.0028; Cleaner than: 27 |
| DNS server | NS: (IP: 162.251.82.250; Host: dns1.regway.com), (IP: 162.251.82.248; Host: dns2.regway.com), (IP: 162.251.82.253; Host: dns4.regway.com), (IP: 162.251.82.118; Host: dns3.regway.com); Zone: thorchain.exchange |
| Quality | Cls: 0; Seo: 91; Si s: 3.21; Fcp s: 1.05; Lcp s: 1.05; Tbt ms: 0; Performance: 99; Accessibility: 93; Best practices: 100 |
| Location | IP: 66.116.209.78; ASN: 31898; Org: Oracle Corporation; City: Phoenix; Country: US |
| SSL | San: thorchain.exchange, www.thorchain.exchange; Bits: 2048; Chain: www.thorchain.exchange, YR2, Root YR, ISRG Root X1; Issuer: Let's Encrypt / YR2; Serial: 06BAF476FE1F4A6E70042738CE7F389EBF27; SHA256: cc7f4d9f424933f8f01f5603f4b2cbc8e7b2ca177f8da32fcaeaf466670f85a4; Subject: www.thorchain.exchange; Valid to: 2027-02-13T02:57:37Z; Valid from: 2026-11-15T02:57:38Z |
| DNS records | A: 66.116.209.78; NS: dns1.regway.com, dns3.regway.com, dns2.regway.com, dns4.regway.com; Soa: Nsname: dns1.regway.com; Hostmaster: shibaswap.onionmail.org; Serial: 2026071503; Refresh: 7200; Retry: 7200; Expire: 172800; Minttl: 38400 |
| 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: ✗ |
| Get IP | IP: 66.116.209.78; Family: 4 |
| Redirects | Chain: https://thorchain.exchange |
| Subdomains | Count: 1; Subdomains: www.thorchain.exchange |
| Tech stack | Technologies: Apache HTTP Server, Open Graph |
| Page links | External: https://www.thorchain.org/, https://www.thorchain.org/privacy-policy, https://www.thorchain.org/terms-of-use, https://x.com/unstoppablebyhs, https://discord.gg/thorchaincommunity; Internal: https://thorchain.exchange/; External count: 5; Internal count: 1 |
| HTTP headers | Headers: Server: Apache; Content type: text/html |
2f45ced6…7e71618 SHA-256 of the prepared copy given to the model: a1cf8bc1…8e28b1a 2f45ced61eee5aaab7a70b293b9192fa24334be75660e88665dd89f287e71618 · 22046 bytes 2f45ced61eee5aaab7a70b293b9192fa24334be75660e88665dd89f287e71618 · 22046 bytes 2f45ced61eee5aaab7a70b293b9192fa24334be75660e88665dd89f287e71618 · 22046 bytes 4c9f093cc5954a68250f104f830d99ad1262f694a9db93cc7d0a0557c0b9911b · 49575 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.
dns1.regway.comdns2.regway.comdns3.regway.comdns4.regway.comnsname: dns1.regway.comhostmaster: shibaswap.onionmail.orgserial: 2026071503refresh: 7200retry: 7200expire: 172800minttl: 38400Location describes the IP network.
cc7f4d9f424933f8f01f5603f4b2cbc8e7b2ca177f8da32fcaeaf466670f85a4thorchain.exchangewww.thorchain.exchangeSaved 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.
www.thorchain.exchangeDomain recordGoogle PageSpeed Insights — mobile performance audit of thorchain.exchange ·
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Network requests: 6 SHA-256 hashes: 6 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-20 03:41 UTC.
Open this scan on URLScan 01a1f709-5050-7349-8e52-354e5cd602d9 ↗
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
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 135 d 12 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 |
|---|
520 stored lookalike domains
Names that imitate the brand, found by dnstwist. A similar name alone does not prove the same owner.
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.
Where to send it:
Nothing matches. Clear the search or choose another filter.
Showing 12 of 520
Showing 100 of 520
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
thorchain.exchange PD-C467661F76570DE798BD Recipient: abuse@publicdomainregistry.com 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 ↗
thorchain.exchange)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.