Skip to security report
Analytics Dashboard
Domain security and threat intelligence
4y5twe3.icu favicon

4y5twe3.icu

In short

4y5twe3.icu is a phishing page detected by PhishDestroy on 2026-08-28. Risk: critical (89/100). Registrar: NicNames. Status: Content unavailable. VirusTotal: 13/89 engines flag it. Listed on Spamhaus DBL. Do not enter credentials or connect a wallet.

Registrar
NicNames
Registered
Aug 25, 2026
PhishDestroy assessment Critical
Availability Content unavailable Content was unavailable in the latest observation Observed · HTTP probe
Risk signals
VirusTotal detections: 13/89 Spamhaus DBL: DBL_PHISH
OTX: 3 refs Aug 28, 2026
API
This domain has been flagged as malicious
Security engines reporting a detection: 13. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
13 / 89
engine detections
Google Safe Browsing
No threat flag
OTX
3
community references
Page captures
2
open gallery
Domain age
58 days
Source evidenceVirusTotal 13 / 89 · OTX 3 references 6 sources

VirusTotal

13 / 89 engine detections

Open report

Spamhaus DBL

DBL_PHISH

OTX

3 community references

Open report

Google Safe Browsing

No threat flag

Open report

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Analysis

Critical
VirusTotal
13 / 89
OTX
3 community refs
Page captures
2
Page captures Source results Registration record

PhishDestroy threat report

Overview

4y5twe3.icu is a domain on the PhishDestroy blocklist. It does not yet have a final scheme classification, and no impersonated brand has been identified. PhishDestroy first saw it on 2026-08-28. The site went offline on 2026-09-13, and as of 2026-10-19 its DNS no longer resolves, so it is currently unreachable.

How the scam works

The main signal is Spamhaus, which lists the domain in its phishing category. That points to a page built to trick visitors into handing over something valuable, such as login credentials, recovery phrases or a wallet connection that grants spending rights. A meaningless string on a cheap TLD is typical of throwaway domains that are spread through links in messages, ads or social posts rather than found by search. No specific lure, brand or kit can be attributed to this site, so the realistic risk is general phishing: anything typed or signed there should be treated as compromised.

Evidence

On 2026-09-13, 13 of 89 VirusTotal engines flagged the domain. Named vendors include alphaMountain.ai, BitDefender, CRDF, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data and Gridinsoft. Agreement among that many unrelated security vendors, together with the Spamhaus DBL phishing listing, is a stronger signal than any single verdict. The domain also appears in 3 AlienVault OTX threat pulses, so other researchers have tracked it independently.

Infrastructure

The name 4y5twe3 is a random-looking string on the .icu TLD, the kind of disposable address that costs little to replace once blocked. Its short lifespan fits that pattern: it stopped serving content on 2026-09-13, about two weeks after PhishDestroy first saw it. The DNS is now inactive.

What to do

If you entered a password or email on this site, change that password everywhere you reused it and turn on app-based two-factor authentication. If you typed a seed phrase or private key, move your funds to a newly created wallet at once, because that phrase can no longer be trusted. If you connected a wallet or signed anything, review and revoke token approvals with a reputable approval checker and watch the wallet for unexpected transfers. Defenders should block the domain at DNS and proxy level, search mail and chat logs for links to it, and keep it blocked in case it comes back online.

Useful links

VirusTotal reportGoogle Safe Browsing statusReport phishing to GoogleSite owner? Request a review

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Cloudflare Radar · 2026-09-13T00:09:25Z

Observed: · Retrieved:

Uuid
79f5ca70-be19-4a08-9ee0-37b2ba3b022d
VirusTotal · 2026-10-19T12:46:14Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 12,
    "suspicious": 4,
    "undetected": 33
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "phishing",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "CyRadar": "phishing",
    "Fortinet": "spam",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "suspicious",
    "Seclookup": "malicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Tags
[
    "dga"
]
Registrar
NicNames, Inc
Created
2026-08-25T14:52:54Z
Expires
2027-08-25T23:59:59Z
Updated
2026-08-30T14:57:19Z
First seen
2026-08-25T16:10:04Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.7.143"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.187.152"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "v=spf1 redirect=icloud.com"
    },
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "jaime.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "TXT",
        "value": "slack-site-verification=DFRCAdGAxNVSOrX61agNOe5pDI0PqPbQFjHq"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::6815:78f"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "jaime.ns.cloudflare.com"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "vera.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:bb98"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "mx01.mail.icloud.com",
        "priority": 10
    }
]
Dns at
2026-08-27T06:58:49Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "4y5twe3.icu",
        "*.4y5twe3.icu"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "94fc5eb73d570ee20efc2de62a74d733",
    "sha256": "0d0a03c07d743a4671060f56d2a9fb30292e79a6bfd9c2e7ba988c30c82fb663",
    "subject": "4y5twe3.icu",
    "valid_to": "2026-11-23T15:11:44Z",
    "valid_from": "2026-08-25T14:12:55Z"
}
Registration record
{
    "registrar": "NicNames, Inc",
    "registrar_iana_id": "4156",
    "registrar_url": "http://www.nicnames.com",
    "created": "2026-08-25T14:52:54Z",
    "updated": "2026-08-28T15:54:39Z",
    "expires": "2027-08-25T23:59:59Z",
    "status": [
        "clientHold",
        "clientTransferProhibited",
        "serverHold",
        "serverTransferProhibited"
    ],
    "nameservers": [
        "jaime.ns.cloudflare.com",
        "vera.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}

Questions about 4y5twe3.icu

Is 4y5twe3.icu legit?

No. PhishDestroy classifies 4y5twe3.icu as a phishing page (risk: critical, 89/100); it was first detected on 2026-08-28. VirusTotal: 13/89 engines flag it. Listed on Spamhaus DBL. Treat the site as unsafe.

Is 4y5twe3.icu safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on 4y5twe3.icu. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used 4y5twe3.icu?

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.

Explore

Blocklist matchesPhishDestroy 1
PhishDestroy PhishDestroy list View source

Stored Capture · 2 captures

URLScan · 2026-08-25 1 / 2
SourceURLScan · 2026-08-25
Recorded2026-08-25 23:30 UTC
StateStored capture
Position1 / 2
Open capture Source Report Wayback Download
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 31 days

Domain details

Domain
OTX tags 2026-08all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar NicNames SE(SE)
Abuse contact["abuse@nicnames.com", "2d8644446d24f14as@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for 4y5twe3.icu →
RegistrationCreated Aug 25, 2026 (58d · New) — Expires Aug 25, 2027
Time to First Unavailability 15 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 28, 2026
SHORTDOT ZONE · PUBLIC EVIDENCE .icu

ShortDot zone evidence

The linked repository preserves daily zone observations across seven ShortDot-operated TLDs, including registration volume and abuse-related indicators. This registry context is supporting background and is not an independent detection for the domain in this report.

ShortDot SA · Luxembourg 7 zones · full-zone evidence updated daily Open the ShortDot evidence repository (GitLab)
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Nameservers 2

  • jaime.ns.cloudflare.com
  • vera.ns.cloudflare.com

Mail routing 1 MX record

  • mx01.mail.icloud.compriority 10

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-08-25 14:12:55
Valid until
2026-11-23 15:11:44
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint0d0a03c07d743a4671060f56d2a9fb30292e79a6bfd9c2e7ba988c30c82fb663
Certificate names · 2 SANs
  • 4y5twe3.icu
  • *.4y5twe3.icu

Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.

Latest Classified Outcome 2026-10-21 14:53:36 UTC

Primary outcome DNS inactive reason: DNS NXDOMAIN 80% confidence
Attribution source: Dns Cache
Evidence layers Availability: DNS inactive Content: Unreachable DNS: NXDOMAIN Registration: Unknown
Latest HTTP observation Unknown Probe Inconclusive 20% 2026-10-21 01:00:13 UTC
RDAP registration Unknown
Observed timeline current episode first observed: 2026-09-30 16:14:55 UTC first terminal observation: 2026-09-30 16:14:55 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

13 / 89 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 13 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
Lionic
SOCRadar
Sophos
VIPRE
Registration & observation details3

Availability observations

Outcome first observed
Observation window ends
Estimate basis
first_observation_only

An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.

Stored observation history12

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

Earlier observations 7
  1. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  2. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  3. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  4. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  5. Availability monitor · Recorded state

    Unknown→dns_inactive

    dns_nxdomain

  6. Availability monitor · Recorded state

    dns_inactive

    dns_nxdomain

  7. Availability monitor · Recorded state

    Reachable→Unavailable

Recorded activity

4 entries
  1. AlienVault OTX

    3 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    13/89 engine detections

    View source
  4. Added to PhishDestroy

    4y5twe3.icu

    View source

Check for cloaking

Compare what a browser and a crawler receive, and check for Keitaro traffic routing.

4y5twe3.icu

Evidence & External Reports

Security Analysis
VirusTotal 13 det. ChainPatrol URLQuery Scamadviser 80 trust SSL Labs Stored certificate dates valid CF Radar Open report OTX 3 refs WOT Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Content unavailable

Listed domains receive at least one abuse report; this entry has no retained notification history.

If credentials were compromised, report immediately. Do not engage with recovery scammers.

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →

Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

Template-based draft · optional AI wording assistance requires separate consent

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

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 4y5twe3.icu)
  • 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)
  • Europol — European cybercrime reporting (EU)
  • 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

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
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.

Request a correction or appeal How PhishDestroy works
Embed this reportA compact widget with a link to the evidence
HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/4y5twe3.icu"
  title="PhishDestroy threat report for 4y5twe3.icu"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>