Skip to security report
Analytics Dashboard
Recorded security signals
Stored VirusTotal result: 3/92 engines flagged. malicious: 2. suspicious: 1. Analysis time (as stored): 2026-11-06T15:57:22Z. Retrieved (as stored): 2026-11-06T18:12:27Z. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
ios.mergentest23.live favicon

ios.mergentest23.live

In short

PhishDestroy first recorded ios.mergentest23.live on 2026-11-06. Stored VirusTotal result: 3/92 engines flagged. malicious: 2. suspicious: 1. Analysis time (as stored): 2026-11-06T15:57:22Z. Retrieved (as stored): 2026-11-06T18:12:27Z.

Review the evidence
Registrar
United StatesDynadot
Resolved IP
United States172.67.180.42Cloudflare, Inc. · CDN
Registered
Oct 9, 2026
First observed
Nov 6, 2026
PhishDestroy assessment High
65/100
Evidence score
First observed Nov 6, 2026 17:00 UTC · PhishDestroy
Risk signals
VirusTotal detections: 3/92 Spamhaus DBL: phishing domain Young domain: 28 days old
VirusTotal
3 / 92
engine detections ·
URLScan
Malicious
engine verdict · score 74
Page captures
1
open gallery
Domain age
28 days
registered 2026-10-09 according to WHOIS
Nov 6, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy first recorded ios.mergentest23.live on 2026-11-06. Stored VirusTotal result: 3/92 engines flagged. malicious: 2. suspicious: 1. Analysis time (as stored): 2026-11-06T15:57:22Z. Retrieved (as stored): 2026-11-06T18:12:27Z. Risk: high (65/100). Registrar: Dynadot. Hosting: Cloudflare, Inc. Do not enter credentials or connect a wallet.

High
VirusTotal
3 / 92
Hosting
United States172.67.180.42Cloudflare, Inc. · CDN
Registrar
United StatesDynadot
Registered
Oct 9, 2026
Page captures
1
Page captures Source results Registration record

Recorded source summary

PhishDestroy stores a record for ios.mergentest23.live. Source observations are dated separately; missing checks do not establish safety.

A reviewed analysis is not available for this text revision. Consult the dated source records below.

Source evidenceVirusTotal 3 / 92 6 sources

VirusTotal

3 / 92 engine detections

Analysis:
Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
55
Malicious
2
Suspicious
1
Undetected
34

Vendor labels

VIPRE
malware
PhishFort
phishing
alphaMountain.ai
suspicious

Reputation score

0

Categories

alphaMountain.ai
Suspicious (alphaMountain.ai)
Forcepoint ThreatSeeker
newly registered websites

First seen

DNS records

  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3033::ac43:b42a
  • TTL, seconds
    300
    Type
    A
    Value
    104.21.51.118
  • TTL, seconds
    300
    Type
    A
    Value
    172.67.180.42
  • TTL, seconds
    300
    Type
    AAAA
    Value
    2606:4700:3037::6815:3376

DNS records observed

JARM fingerprint

27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c

Certificate

Subject alternative names
  • *.mergentest23.live
  • mergentest23.live
Issuer
Let's Encrypt / YE1
Serial
643ae4791837e5b63c498aef6593f9cac6e
SHA-256
675f9708817e98772904fb5979e6ad8e7dceb7b4147fbf1b0f36469c52d82821
Subject
mergentest23.live
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 55,
    "malicious": 2,
    "suspicious": 1,
    "undetected": 34
}
Vendor labels
{
    "VIPRE": "malware",
    "PhishFort": "phishing",
    "alphaMountain.ai": "suspicious"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Suspicious (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "newly registered websites"
}
First seen
2026-11-06T15:57:24Z
DNS records
[
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3033::ac43:b42a"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.51.118"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.180.42"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3037::6815:3376"
    }
]
Dns at
2026-11-06T15:57:24Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "*.mergentest23.live",
        "mergentest23.live"
    ],
    "issuer": "Let's Encrypt / YE1",
    "serial": "643ae4791837e5b63c498aef6593f9cac6e",
    "sha256": "675f9708817e98772904fb5979e6ad8e7dceb7b4147fbf1b0f36469c52d82821",
    "subject": "mergentest23.live",
    "valid_to": "2027-01-15T11:51:40Z",
    "valid_from": "2026-10-17T11:51:41Z"
}
Separate collector summary

This is a separate stored result. Its counts, vendors and dates do not replace the provider observation above. A retrieval date is not an analysis date.

source
VirusTotal
scope
unknown
result_state
observed
numerator
3
denominator
92
malicious
null
suspicious
null
vendors
["alphaMountain.ai","PhishFort","VIPRE"]
observed_at
2026-11-06 15:57:22
checked_at
2026-11-06 19:12:32
fetched_at
2026-11-06 18:12:33
time_basis
as stored; legacy timezone not established

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 74

SHA-256 508ce15d2c2a753e164186231cd1860c9df9fd8bacc86ceb8a71d8f4ce2bf8b1

Open report
URLScanOriginal source recordObserved: 18 fields

Observed: · Retrieved:

Report ID

01a1b193-5af4-7720-bf58-bbacf440f9db

Final URL

https://ios.mergentest23.live/

HTTP response

522

Redirect type

https-only

Redirects

  • To
    https://ios.mergentest23.live/
    From
    http://ios.mergentest23.live/
    Status
    307
  • To
    http://ios.mergentest23.live/
    From
    https://ios.mergentest23.live/
    Status
    307
  • To
    https://ios.mergentest23.live/
    From
    http://ios.mergentest23.live/
    Status
    307

IP address

172.67.180.42

Contacted IP addresses

  • 172.67.180.42

Autonomous systems (ASN)

  • 13335

Linked domains

  • www.cloudflare.com
  • developers.cloudflare.com

Document hash

508ce15d2c2a753e164186231cd1860c9df9fd8bacc86ceb8a71d8f4ce2bf8b1

TLS session and certificate

Subject alternative names
  • *.mergentest23.live
  • mergentest23.live
Cipher
AES_128_GCM
Issuer
YE1
Subject
mergentest23.live
Protocol
QUIC
Valid until
Valid from

Domain age, days

0

Registered domain age, days

27

Certificate age, days

20

Certificate validity, days

89

Page requests

8

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-2aab354
Score
74
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
cloudflare
Content-type
text/html; charset=UTF-8
X-frame-options
SAMEORIGIN
Referrer-policy
same-origin
Priority
u=0,i
Original source fields · JSON
Uuid
01a1b193-5af4-7720-bf58-bbacf440f9db
Final url
https://ios.mergentest23.live/
Status
522
Redirected
https-only
Redirects
[
    {
        "to": "https://ios.mergentest23.live/",
        "from": "http://ios.mergentest23.live/",
        "status": 307
    },
    {
        "to": "http://ios.mergentest23.live/",
        "from": "https://ios.mergentest23.live/",
        "status": 307
    },
    {
        "to": "https://ios.mergentest23.live/",
        "from": "http://ios.mergentest23.live/",
        "status": 307
    }
]
Ip
172.67.180.42
Contacted IP addresses
[
    "172.67.180.42"
]
Asns
[
    "13335"
]
Linked domains
[
    "www.cloudflare.com",
    "developers.cloudflare.com"
]
Document hash
508ce15d2c2a753e164186231cd1860c9df9fd8bacc86ceb8a71d8f4ce2bf8b1
Tls
{
    "san": [
        "*.mergentest23.live",
        "mergentest23.live"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "YE1",
    "subject": "mergentest23.live",
    "protocol": "QUIC",
    "valid_to": "2027-01-15T11:51:40Z",
    "valid_from": "2026-10-17T11:51:41Z"
}
Domain age days
0
Apex age days
27
Tls age days
20
Tls valid days
89
Requests
8
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-2aab354"
        ],
        "score": 74,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html; charset=UTF-8",
    "x-frame-options": "SAMEORIGIN",
    "referrer-policy": "same-origin",
    "priority": "u=0,i"
}
Separate monitor record · date not recorded

Separate stored monitor snapshot; does not replace the primary report record or establish current availability.

record_source
domain_monitor.urlscan
uuid
01a1b193-5af4-7720-bf58-bbacf440f9db
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no 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.

Collected source details

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

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 10 fields

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1
  • TLSv1.1
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80
  • 443
  • 8080

DNS servers

Nameservers
  • IP address
    172.64.32.207
    Host
    nadia.ns.cloudflare.com
  • IP address
    172.64.35.50
    Host
    damian.ns.cloudflare.com
DNS zone
mergentest23.live

Location

IP address
2606:4700:3033::ac43:b42a
ASN
13335
Organization
Cloudflare, Inc.
City
San Francisco
Country
US

TLS certificate

Issuer
Let's Encrypt / YE1
Subject
mergentest23.live

DNS records

A
  • 172.67.180.42
  • 104.21.51.118
AAAA
  • 2606:4700:3037::6815:3376
  • 2606:4700:3033::ac43:b42a

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

Web application firewall

WAF product
Cloudflare
WAF detected
Yes

IP lookup

IP address
2606:4700:3037::6815:3376
IP version
6
Original source fields · JSON
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1",
        "TLSv1.1",
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443,
        8080
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "172.64.32.207",
            "host": "nadia.ns.cloudflare.com"
        },
        {
            "ip": "172.64.35.50",
            "host": "damian.ns.cloudflare.com"
        }
    ],
    "zone": "mergentest23.live"
}
Location
{
    "ip": "2606:4700:3033::ac43:b42a",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "San Francisco",
    "country": "US"
}
Ssl
{
    "issuer": "Let's Encrypt / YE1",
    "subject": "mergentest23.live"
}
DNS records
{
    "A": [
        "172.67.180.42",
        "104.21.51.118"
    ],
    "AAAA": [
        "2606:4700:3037::6815:3376",
        "2606:4700:3033::ac43:b42a"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3037::6815:3376",
    "family": 6
}

Questions about ios.mergentest23.live

Is ios.mergentest23.live legit?

PhishDestroy rates ios.mergentest23.live as high risk (65/100) from the recorded evidence; it was first recorded on 2026-11-06. Stored VirusTotal result: 3/92 engines flagged. malicious: 2. suspicious: 1. Analysis time (as stored): 2026-11-06T15:57:22Z. Retrieved (as stored): 2026-11-06T18:12:27Z. The local score and a listing do not prove fraud. Check each source’s date and the exact URL.

Is ios.mergentest23.live safe to connect a wallet?

This report does not record which wallet requests ios.mergentest23.live 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 ios.mergentest23.live?

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.

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 1 capture

URLScan · 2026-11-06 1 / 1
SourceURLScan · 2026-11-06
Recorded
StateStored capture
HTTP status522
Final URLhttps://ios.mergentest23.live/
Position1 / 1
Open capture Source Report Wayback Download
All capture links and hashes (1)
TLS Certificate
Issued by Let's Encrypt / YE1 · stored validity ends in 69 days

Domain details

Domain
IP Context United States172.67.180.42 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Registrar (base domain) Dynadot US(US)
Abuse contact["abuse@dynadot.com"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for mergentest23.live →
Registration (base domain)mergentest23.live · Created Oct 9, 2026 (28d · Very New!) — Expires Oct 9, 2027
Technical detailsProvenance & timestamps
First DetectedNov 6, 2026
Submitted URLhttps://ios.mergentest23.live/
ICANN OVERSIGHT Registration: mergentest23.live

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For the registrable domain mergentest23.live behind this subdomain, 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

Shared CDN edge
Resolved IP
United States172.67.180.42
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
United StatesSan Francisco, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • nadia.ns.cloudflare.com
  • damian.ns.cloudflare.com

Location describes the IP network.

TLS certificate

Issuer
Let's Encrypt / YE1
Valid from
2026-10-17 11:51:41
Valid until
2027-01-15 11:51:40
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint675f9708817e98772904fb5979e6ad8e7dceb7b4147fbf1b0f36469c52d82821
Certificate names · 2 SANs
  • *.mergentest23.live
  • mergentest23.live

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

viewdns.info · 172.67.180.42rapiddns.io
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 3 detections
VIPRE
PhishFort
alphaMountain.ai

Captured network requests

Network requests: 8 SHA-256 hashes: 7 URLScan 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-11-06 17:05 UTC.

Open this scan on URLScan 01a1b193-5af4-7720-bf58-bbacf440f9db ↗

All retained availability observations2

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.

  1. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-06 18:01:24.000000
    Evidence SHA-256
    3c54ebf14ddabbf5c7272f3918d6d26999d1b692ef87d1f11f4d49b786862657
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 18:01:24
    Evidence reason
  2. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-06 18:01:24.000000
    Evidence SHA-256
    3c54ebf14ddabbf5c7272f3918d6d26999d1b692ef87d1f11f4d49b786862657
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-11-06 18:01:24
    Evidence reason

Threat Response Pipeline

  1. Discovery · recorded
  2. Analysis · recorded
  3. Monitoring · recorded

Recorded events: 8. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Pre-emptive Discovery & IngestionThreat Ingested Recorded: 1 of 1
  • Threat Ingested
    ios.mergentest23.live detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · VirusTotal · Forensic Evidence Collected Recorded: 6 of 6
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 74
  • Cloudflare Radar Report
    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.
  • VirusTotal
    Detections recorded on VirusTotal: 3/92
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
Publication & AvailabilityDestroyList Published Recorded: 1 of 1

Recorded activity

3 entries
  1. Added to PhishDestroy

    ios.mergentest23.live

    View source
  2. VirusTotal

    3/92 engine detections

    View source
  3. URLScan

    Malicious · engine verdict · score 74

    View source
How we investigate & report

Public scans, evidence and abuse channels

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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk 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
All stored records by source

Browse this domain’s complete history by source. The download includes every record of the selected source. Dates retain their original field labels.

Download all records as JSON

Check for cloaking

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

ios.mergentest23.live

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 3 det. ChainPatrol URLQuery SSL Labs Stored certificate dates valid CF Radar Open report WOT ScamAdviser 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?

3 evidence signal groups linked Unverified
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.

Immediate steps Find reporting contacts

Official reporting routes

Chainabuse
Report a crypto wallet, transaction, or phishing URL
SEAL-ISAC
Security Alliance crypto threat intelligence
More official reporting routes
FTC ReportFraud United States

Report scams and fraud to the US Federal Trade Commission. Reports go into a database used by law enforcement.

IdentityTheft.gov United States

Official identity theft report with a step-by-step recovery plan.

CISA United States

Report cyber incidents and phishing to the US Cybersecurity and Infrastructure Security Agency.

CSIRTs Network European Union

Directory of national incident response teams (CSIRTs) in the EU. Find the team for your country.

FIRST Worldwide

Worldwide directory of incident response teams, searchable by country and sector.

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

Report scams to the National Anti-Scam Centre run by the ACCC.

PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect

Report to Your Local Authorities

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

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 ios.mergentest23.live)
  • 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

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.

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/ios.mergentest23.live"
  title="PhishDestroy threat report for ios.mergentest23.live"
  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>