ABUSE NOTICE · 7D+ OPEN
Outgoing abuse reports are recorded; the latest stored availability evidence still shows the domain reachable.
Notification and current-status evidence
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@publicdomainregistry.com.
The latest stored availability evidence still shows the domain reachable; 7 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.
SSL certificate is invalid or expired. Issuer: Let's Encrypt / YR1
証拠の概要
クリティカル
VirusTotal
19/91
OTX
4 community refs
URLScan
Stored capture
Assessment
trezor-suitetrezor.us was first observed on 2026-10-04, and as of 2026-10-05, it was recorded on both MetaMask and SEAL blocklists. The domain was also internally listed by PhishDestroy, indicating that multiple sources have noted its presence within a short period.
Recorded Evidence
MetaMask listed trezor-suitetrezor.us on its blocklist on 2026-10-05. SEAL also included the domain on its blocklist on 2026-10-05. The domain was first observed on 2026-10-04 and registered with ENOM, INC. on 2025-08-06. Its SSL certificate, issued by Let's Encrypt / YR1, was scanned on 2026-10-04. PhishDestroy internally listed the domain as well.
Interpretation
The blocklist records from MetaMask and SEAL, along with the internal listing by PhishDestroy, provide several points of reference for trezor-suitetrezor.us. The close timing between the domain's first observation and its inclusion on external blocklists may be useful for examining its recent activity. Registration and SSL certificate details offer context about its technical setup, but do not reflect its current content or use.
Recommended Actions
For trezor-suitetrezor.us, it is advisable to preserve the blocklist entries from MetaMask and SEAL, as well as the internal listing from PhishDestroy. Comparing these records can help track any changes or updates related to the domain. Continued monitoring of external blocklists is recommended to observe further developments.
Certificate fingerprinta32bf8330332da9976da6743469a2344d441eb1d369d28ab63d29b5828595a4eCertificate names · 4 SANs
bitcoinwallet-t.us
www.bitcoinwallet-t.us.ledgerlive-ledgers.us
www.trezor-suitetrezor.us.ledgerlive-ledgers.us
www.wa-atomic.us.ledgerlive-ledgers.us
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-11 02:13:50 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 02:13:50 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
脅威情報の照合 · source references
ScamAdviserPublic lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
Last analyzed First positive detection Previous stored snapshot: 19 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CyRadar
Ermes
ESET
Emsisoft
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
カスペルスキー
Lionic
ネットクラフト
SOCRadar
ソフォス
URLQuery
VIPRE
Webroot
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-04 05:20:50 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 66.116.229.240.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
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.
Blocklist hits included with submission:MetaMask, SEAL
PDF notice generated Notice text archived (650 chars)
Abuse notice text as sent to the provider
Policy Violations:
Illegal Activities: Active phishing operation targeting victims
Fraud & Deception: Impersonation of legitimate services
Identity Theft: Collection of credentials under false pretenses
Applicable Laws (Unknown):
International Anti-Cybercrime Regulations
Budapest Convention on Cybercrime
Universal Fraud Prevention Laws
Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws.
Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
