PhishDestroy rates duplicate-disabled-522922.invalid as critical risk (98/100) from the recorded evidence; it was first recorded on 2026-08-18. VirusTotal: 12/91 engines flag it. Treat the site as unsafe.
Is duplicate-disabled-522922.invalid safe to connect a wallet?
This report does not record which wallet requests duplicate-disabled-522922.invalid makes. Because of the risk signals above, do not connect a wallet, sign messages or approve token permissions there. A confirmed blockchain transaction cannot be reversed.
What should I do if I used duplicate-disabled-522922.invalid?
It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.
Differs from the registration date in WHOIS (2025-10-29), which gives 47 days on the scan date 2025-12-15. The two sources disagree; both values are kept as recorded.
Registered domain age, days
1139
Differs from the registration date in WHOIS (2025-10-29), which gives 47 days on the scan date 2025-12-15. The two sources disagree; both values are kept as recorded.
Differs from the registration date in WHOIS (2025-10-29), which gives 47 days on the scan date 2025-12-15. The two sources disagree; both values are kept as recorded.
Apex age days
1139
Differs from the registration date in WHOIS (2025-10-29), which gives 47 days on the scan date 2025-12-15. The two sources disagree; both values are kept as recorded.
RegistrationCreated Oct 29, 2025 —Expires Oct 29, 2026
Time to First Unavailability37 days
What we count Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 18, 2026
DOM Analysisanalyzed Sep 17, 2026score 98/100
Favicon Hash
ICANN OVERSIGHT
Accreditation and RAA context
Registrar accreditation and DNS abuse obligations
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.
Accreditation is a contract, not a safety certification.
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.
Accountability draft Nothing is sent automatically.
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
185.53.179.109
Network ASN
AS61969
Organization
TEAM-INTERNET
Observed location
Munich, DE
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 1
ns2.muumuu-domain.com
Location describes the IP network.
TLS certificate
Issuer
WE1
Valid from
2025-10-29 04:46:53
Valid until
2026-01-27 05:44:34
Hostname coverage
Certificate hostname mismatch
Validity
Stored certificate expired
Collection time
2026-09-18 22:02:28 UTC
Collection source
PhishDestroy collector
Certificate names · 2 SANs
tetherusdtwallet.com
*.tetherusdtwallet.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Captured network requests
Network requests: 8SHA-256 hashes: 8URLScan 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-10-29 03:04 UTC.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
duplicate-disabled-522922.invalid
Saved result
Unreachable
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 · Recorded state
Reachable→Unavailable
All retained availability observations32
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: 10. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Pre-emptive Discovery & IngestionThreat Ingested1/1Recorded: 1 of 1
Threat Ingested
duplicate-disabled-522922.invalid detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · Cloudflare Radar Report · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded · Content Observed Unavailable6/6Recorded: 6 of 6
A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
OTX Community References
Community publication references on AlienVault OTX: 25. References are not vendor verdicts and are excluded from the evidence score.
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
Technical Analysis Recorded
The report contains stored results of technology detection or forensic analysis.
Content Observed Unavailable
Monitoring recorded an unavailable response; the cause was not independently established.
Publication & AvailabilityDestroyList Published · Content Observed Unavailable · Time to First Unavailability3/3Recorded: 3 of 3
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.
Supporting signal — Shares a page feature, infrastructure or a collector label; not proof of one operator.
Discovery only — Same registrar or CDN edge: listed for navigation, not evidence of a link.
Each spoke is one reason a domain is linked to this report. Node size marks VirusTotal detections, dashed nodes are already offline, and the full lists follow below. Full list of related reports
Content matches2
Same favicon file hash, or a recorded page title that starts with the same 20 characters. A content match does not establish a shared phishing kit or owner.
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. Silence is the scammer’s greatest advantage. Break it.
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.
If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.
Scammers are criminals. Filing a report creates a legal record and helps protect others.
97-country directory
Template-based draft • optional AI wording assistance requires separate consent
Review and submit it yourself
After a phishing incident
Recommendations & Advice for Victims
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
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 duplicate-disabled-522922.invalid)
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.
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.
185.53.179.109TEAM-INTERNET · CDN
GoogleSafe Browsing↗ 
MicrosoftSmartScreen↗ 
VirusTotalURL analysis↗ 
CloudflareRadar / abuse reporting↗ 
YandexSafe Browsing↗ 
URLScan.ioPublic scan↗ 
ESETSample / URL submission↗ 
BitdefenderURL submission↗ 
NortonSafe Web↗ 
SymantecSiteReview↗ 
AviraURL reporting↗ 
Avast / AVGURL reporting↗ 
KasperskyOpenTIP↗ 
Dr.WebOnline scanner↗ 
NetcraftAbuse reporting↗ 
PhishTankCommunity reporting↗ 
APWG eCXPhishing intelligence↗ 
PhishStatsPublic feed↗ 
Phish.ReportHosting abuse↗ 
SpamhausDomain reputation↗ 
PolySwarmMulti-engine analysis↗ 
CheckPhishURL scan↗ 
QutteraMalware scan↗ 
URLqueryBrowser analysis↗ 
Criminal IPAsset intelligence↗ 
CRDFThreat Center↗ 
ScamadviserReputation check↗ 
MyWOTCommunity reputation↗ 
