VirusTotal
4 / 92 engine detections
Open reportfe.echo-test.uk is a MetaMask impersonation page detected by PhishDestroy on 2026-10-11. Risk: critical (80/100). Registrar: 123-Reg. Status: Last known active. Hosting: IOMART-AS IOMART CLOUD SERVICES LIMITED, GB. PhishDestroy sent 1 abuse report. VirusTotal: 4/92 engines flag it. Do not enter credentials or connect a wallet.
“Echo”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@rapidswitch.com.
The latest stored availability evidence still shows the domain reachable; 11 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.
4 / 92 engine detections
Open report3 det.
Open reportno community references
Open reportprovider verdict: clean
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
fe.echo-test.uk is an impersonation phishing page that presents itself under the name "Echo" to pass as a legitimate service. Wallet-provider and security-alliance blocklists have flagged it, so its likely targets are crypto users who expect to find Echo there. PhishDestroy first detected it on 2026-10-11. On 2026-10-19 the site was still online and serving its content.
Impersonation pages like this copy the name and look of a known service, here branded "Echo", so visitors believe they are on the real thing. The visitor is then pushed into an action that hands control to the operator. That can mean typing login details, a recovery phrase or a private key, connecting a wallet, or signing a transaction or approval. Credentials let attackers take over accounts. A seed phrase or a malicious signature lets them move funds out of the wallet, and crypto transfers of this kind cannot be reversed.
MetaMask and SEAL both list the domain alongside PhishDestroy, which means several groups focused on crypto threats reached the same verdict on their own. VirusTotal coverage is still thin. As of 2026-10-16, 4 of 92 engines flagged it: alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar. Because of that low count, many browsers and security tools may not warn visitors yet.
The domain was registered on 2025-11-19 through 123-Reg Limited (t/a 123-reg), almost eleven months before PhishDestroy detected it. That gap suggests the domain was set up well in advance or used quietly before it was exposed. The "fe" subdomain on a name containing "test" fits a staging-style host rather than a brand's real site. It runs on the IOMART Cloud Services network in Great Britain, and its free Let's Encrypt certificate only means the padlock icon proves nothing about who runs the site.
Do not connect a wallet to this site or type any phrase or password into it. If you connected a wallet or signed anything there, review and revoke token approvals for that address, then move remaining assets to a new wallet whose seed phrase has never been entered online. If you entered a seed phrase or private key, treat that wallet as fully compromised. If you entered a password, change it everywhere you reused it and turn on app-based 2FA. Defenders should block the domain and its subdomains, check logs for any visits, and report it to the hosting network and the registrar.
Stored page, network and scanner observations, grouped by source and observation time.
Observed: · Retrieved:
| Uuid | 01a12aae-44b7-769a-b57d-1d5e118b4b9d |
|---|---|
| Final url | https://fe.echo-test.uk/ |
| Status | 200 |
| Redirected | https-only |
| Redirects | [
{
"to": "https://fe.echo-test.uk/",
"from": "http://fe.echo-test.uk/",
"status": 307
}
] |
| Ip | 95.154.198.137 |
| Contacted domains | [
"fonts.gstatic.com",
"fonts.googleapis.com",
"be.echo-test.uk"
] |
| Contacted IP addresses | [
"172.217.222.94",
"172.253.63.95",
"95.154.198.137"
] |
| Asns | [
"15169",
"20860"
] |
| Countries | [
"US",
"GB"
] |
| Document hash | 3a54d7b7eb5be10357ca2e880a24bdd2845c9699f4fd4e50972375b25490e722 |
| Script hashes | [
"82233e7c65776d17ddaa66ecde6b52f3d5648e494e98074f1efcd6a07ac399d7"
] |
| Globals | [
"__reactRouterVersion",
"__framePainter"
] |
| Cookies | [
"XSRF-TOKEN",
"projectecho-session"
] |
| Tls | {
"san": [
"echo-test.uk",
"fe.echo-test.uk",
"www.echo-test.uk"
],
"cipher": "AES_128_GCM",
"issuer": "YE1",
"subject": "echo-test.uk",
"protocol": "TLS 1.3",
"valid_to": "2026-12-10T10:53:44Z",
"valid_from": "2026-09-11T10:53:45Z"
} |
| Domain age days | 317 |
| Apex age days | 325 |
| Tls age days | 30 |
| Tls valid days | 89 |
| Requests | 13 |
| Provider verdicts | {
"engines": {
"tags": [
"urlscan-ml",
"urlscan-ml-60c5e22"
],
"score": 95,
"malicious": true
},
"overall": {
"score": 0,
"malicious": false
}
} |
| HTTP headers | {
"server": "nginx/1.20.1",
"content-type": "text/html"
} |
Observed: · Retrieved:
| Uuid | d4c55a1f-db67-4de0-8395-3a6628c17df7 |
|---|---|
| Final url | https://fe.echo-test.uk/ |
| Status | 200 |
| History | [
{
"url": "https://fe.echo-test.uk/",
"status": 200
}
] |
| DOM structure hash | 84488142a51e293317e0ba8a45ed03a42388529549c37359db813e2496f62b2b |
| Document hash | 3a54d7b7eb5be10357ca2e880a24bdd2845c9699f4fd4e50972375b25490e722 |
| Radar rank | {
"bucket": ">200000"
} |
| DNS records | [
{
"name": "be.echo-test.uk",
"type": "A",
"value": "95.154.198.137"
},
{
"name": "fe.echo-test.uk",
"type": "A",
"value": "95.154.198.137"
}
] |
| Dnssec valid | false |
| Ip | 95.154.198.137 |
| Registration record | {
"registrar": "123-Reg Limited t/a 123-reg",
"created": "2025-11-19T14:59:08Z",
"updated": "2025-11-19T15:07:10Z",
"expires": "2027-11-19T14:59:08Z",
"nameservers": [
"julissa.ns.cloudflare.com.",
"rex.ns.cloudflare.com."
]
} |
Observed: · Retrieved:
| Vendor result counts | {
"timeout": 0,
"harmless": 55,
"malicious": 2,
"suspicious": 2,
"undetected": 33
} |
|---|---|
| Vendor labels | {
"SOCRadar": "suspicious",
"Gridinsoft": "suspicious",
"alphaMountain.ai": "phishing",
"Forcepoint ThreatSeeker": "phishing"
} |
| Reputation | 0 |
| Categories | {
"alphaMountain.ai": "Phishing (alphaMountain.ai)",
"Forcepoint ThreatSeeker": "phishing and other frauds"
} |
| Created | 2025-11-19T00:00:00Z |
| Updated | 2025-11-19T00:00:00Z |
| First seen | 2025-11-27T16:23:26Z |
| DNS records | [
{
"ttl": 300,
"type": "A",
"value": "95.154.198.137"
}
] |
| Dns at | 2026-10-20T02:00:29Z |
| Jarm | 27d40d40d00040d00042d43d0000004ac24e77d76646867f0f6a0c6d9b9bb0 |
| Certificate | {
"san": [
"echo-test.uk",
"fe.echo-test.uk",
"www.echo-test.uk"
],
"issuer": "Let's Encrypt / YE1",
"serial": "674b264424cc677055960ad82b51af85cfe",
"sha256": "9c180a0c050c095f028834292c100ae52c1d9a36bdb920285c8ea09817773276",
"subject": "echo-test.uk",
"valid_to": "2026-12-10T10:53:44Z",
"valid_from": "2026-09-11T10:53:45Z"
} |
No. PhishDestroy classifies fe.echo-test.uk as a MetaMask impersonation page (risk: critical, 80/100); it was first detected on 2026-10-11. VirusTotal: 4/92 engines flag it. Treat the site as unsafe.
No. Do not connect a wallet, sign messages or approve tokens on fe.echo-test.uk. 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
Location describes the IP network.
9c180a0c050c095f028834292c100ae52c1d9a36bdb920285c8ea09817773276echo-test.ukwww.echo-test.ukSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of fe.echo-test.uk · checked Oct 12, 2026
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=https_proxy; location=https://www.echo-test.uk/; server=nginx/1.20.1
fe.echo-test.uk
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unknown→redirected
http_redirect
live_content→redirected
http_redirect
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
Reachable
No threat flag
View source4/92 engine detections
View sourcePD-20261011-28AE26
fe.echo-test.uk
View sourcePage captured
View source79 stored lookalike domains
PD-20261011-28AE26 Recipient: abuse@rapidswitch.com 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 ↗
fe.echo-test.uk)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.