VirusTotal
9 / 92 engine detections
Open reporttrezorauthentication.com is a Trezor impersonation page detected by PhishDestroy on 2026-10-03. Risk: critical (95/100). Registrar: IONOS SE. Status: Last known active. Hosting: IONOS-AS IONOS SE, DE. VirusTotal: 9/92 engines flag it. Do not enter credentials or connect a wallet.
9 / 92 engine detections
Open report1 community reference
Open reportScan report
Open reportNo threat flag
Open reportNo malicious flag
Open reportResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
trezorauthentication.com is an impersonation phishing page posing as Trezor, the hardware wallet maker, and it targets people who keep crypto on a Trezor device. The domain name suggests an official authentication or device-check step, which Trezor does not run through a separate website. PhishDestroy first detected it on 2026-10-03. As of 2026-10-19 the site was still online and serving its content.
Fake Trezor sites usually tell visitors that their device needs to be authenticated, verified or updated, then ask them to type in their 12- or 24-word recovery seed. That seed is the master key to the wallet. Anyone who holds it can recreate the wallet on their own device and empty it, without the physical Trezor and without the PIN. A genuine Trezor device never asks you to enter your seed on a website, so any page that does is stealing it.
On 2026-10-07, 9 of 92 VirusTotal engines flagged the domain. The flagging vendors include BitDefender, CRDF, Forcepoint ThreatSeeker, Fortinet, G-Data, Gridinsoft, Kaspersky and SOCRadar. That count is modest, but it comes from several unrelated security vendors and points the same way. The domain also appears on the MetaMask and SEAL blocklists alongside PhishDestroy's own, and it is referenced in one AlienVault OTX threat pulse.
The domain was registered on 2026-09-30, three days before PhishDestroy caught it. That short gap is typical of throwaway phishing domains set up to be used quickly. Registration went through IONOS SE, and the site is hosted on IONOS's network at an address located in the United States. It was still live more than two weeks after first detection.
If you entered your recovery seed on this site, treat that wallet as fully compromised. Set up a new Trezor wallet with a freshly generated seed on your device and move all remaining funds there immediately. If you also connected a software wallet, revoke any token approvals you granted. If you only browsed the page and typed nothing, no action is needed beyond closing it. Defenders should block the domain at DNS and web proxies and add it to mail and chat filters. Report it to IONOS SE as the registrar and host so the takedown can proceed.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a0f661-9966-713f-9f8e-13b58329dda3 |
|---|---|
| Final url | http://trezorauthentication.com/ |
| Status | 200 |
| Redirects | [
{
"to": "https://trezorauthentication.com/",
"from": "http://trezorauthentication.com/",
"status": 307
},
{
"to": "http://trezorauthentication.com/",
"from": "https://trezorauthentication.com/",
"status": 307
}
] |
| Ip | 74.208.236.56 |
| Ptr | 74-208-236-56.elastic-ssl.ui-r.com |
| Contacted domains | [
"cors.uicdn.net"
] |
| Contacted IP addresses | [
"217.160.86.60",
"74.208.236.56"
] |
| Asns | [
"8560"
] |
| Countries | [
"DE",
"US"
] |
| Linked domains | [
"www.ionos.ca",
"my.ionos.ca"
] |
| Document hash | 933d939fea8a1123e1f88d9b23d9e44196773b930eff6d8405362a8494db2fb9 |
| Globals | [
"f"
] |
| Domain age days | 0 |
| Apex age days | 0 |
| Requests | 14 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 20,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "Apache",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 47,
"malicious": 9,
"suspicious": 2,
"undetected": 34
} |
|---|---|
| Vendor labels | {
"CRDF": "malicious",
"G-Data": "phishing",
"Lionic": "phishing",
"Sophos": "phishing",
"Fortinet": "phishing",
"URLQuery": "suspicious",
"Kaspersky": "phishing",
"Gridinsoft": "suspicious",
"BitDefender": "phishing",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Phishing, Newly Registered (alphaMountain.ai)"
} |
| Registrar | IONOS SE |
| Created | 2026-09-30T18:42:40Z |
| Expires | 2027-09-30T18:42:40Z |
| Updated | 2026-09-30T18:42:45Z |
| First seen | 2026-10-02T17:07:52Z |
| DNS records | [
{
"ttl": 3600,
"type": "A",
"value": "74.208.236.56"
},
{
"ttl": 21600,
"type": "NS",
"value": "ns1080.ui-dns.com"
},
{
"ttl": 3600,
"type": "TXT",
"value": "v=spf1 include:_spf-us.ionos.com ~all"
},
{
"ttl": 21600,
"type": "SOA",
"rname": "hostmaster.1und1.com",
"value": "ns1120.ui-dns.org"
},
{
"ttl": 3600,
"type": "MX",
"value": "mx00.ionos.com",
"priority": 10
},
{
"ttl": 3600,
"type": "MX",
"value": "mx01.ionos.com",
"priority": 10
},
{
"ttl": 3600,
"type": "AAAA",
"value": "2607:f1c0:100f:f000::200"
},
{
"ttl": 21600,
"type": "NS",
"value": "ns1120.ui-dns.org"
},
{
"ttl": 21600,
"type": "NS",
"value": "ns1105.ui-dns.biz"
},
{
"ttl": 21600,
"type": "NS",
"value": "ns1100.ui-dns.de"
}
] |
| Dns at | 2026-10-07T02:01:20Z |
| Registration record | {
"registrar": "IONOS SE",
"registrar_iana_id": "83",
"registrar_url": "http://www.ionos.com",
"created": "2026-09-30T18:42:40Z",
"updated": "2026-09-30T18:42:45Z",
"expires": "2027-09-30T18:42:40Z",
"status": [
"clientTransferProhibited"
],
"nameservers": [
"ns1080.ui-dns.com",
"ns1100.ui-dns.de",
"ns1105.ui-dns.biz",
"ns1120.ui-dns.org"
],
"dnssec": "unsigned"
} |
| Registry data | {
"status": [
"client transfer prohibited"
],
"events": {
"last changed": "2026-09-30T18:42:45Z",
"registration": "2026-09-30T18:42:40Z",
"registrar expiration": "2027-09-30T18:42:40Z",
"last update of RDAP database": "2026-10-02T17:09:58Z"
}
} |
No. PhishDestroy classifies trezorauthentication.com as a Trezor impersonation page (risk: critical, 95/100); it was first detected on 2026-10-03. VirusTotal: 9/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on trezorauthentication.com. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
Last checked
ns1120.ui-dns.orgmx01.ionos.compriority 10mx00.ionos.compriority 10Location describes the IP network.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
Unknown→live_content
content_served
No threat flag
View source9/92 engine detections
View source1 community references
View sourcetrezorauthentication.com
View source74 stored lookalike domains
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
trezorauthentication.com
Listed domains receive at least one abuse report; this entry has no retained notification history.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Choose 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 ↗
trezorauthentication.com)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.