Skip to security report
Analytics Dashboard
Domain security and threat intelligence
axonme.cc favicon

axonme.cc

In short

axonme.cc is a phishing page detected by PhishDestroy on 2026-10-22. Risk: critical (100/100). Registrar: Cloudflare. Status: Last known active. Hosting: Cloudflare, Inc. VirusTotal: 14/92 engines flag it. Do not enter credentials or connect a wallet.

“Axon Middle East FZE”

Registrar
Cloudflare
Resolved IP
104.21.66.124
Registered
Feb 11, 2025
PhishDestroy assessment Critical
Availability Last known active Latest stored reachability observation Observed · HTTP probe
Risk signals
VirusTotal detections: 14/92
OTX: 5 refs Oct 22, 2026 CDN
API
This domain has been flagged as malicious
Security engines reporting a detection: 14. Exercise extreme caution — do not enter credentials or personal information.
VirusTotal
14 / 92
engine detections
Google Safe Browsing
No threat flag
OTX
5
community references
Page captures
4
open gallery
Domain age
618 days
Source evidenceVirusTotal 14 / 92 · OTX 5 references 5 sources

VirusTotal

14 / 92 engine detections

Open report

OTX

5 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
14 / 92
OTX
5 community refs
Page captures
4
Page captures Source results Registration record

PhishDestroy threat report

Overview

PhishDestroy has listed axonme.cc as a suspicious domain based on automated security‑engine detections. The recorded page title reads “Axon Middle East FZE”. The domain was first seen by PhishDestroy on 2026-10-22 and returned an HTTP 200 response on that date.

How the scam works

The detections do not point to a single concrete attack vector; they indicate a generic risk of phishing or malware distribution. No specific malicious behavior was observed on the fetched page, so the assessment remains a broad suspicion rather than a confirmed scheme.

Evidence

VirusTotal scanned the domain on 2026-10-11 (retrieved 2026-10-22) and reported 14 malicious detections out of 92 engines, including BitDefender, Fortinet and G‑Data. Google Safe Browsing checked on 2026-10-22 and reported no threat. URLScan captured the site on 2026-10-22; its engine verdict flagged the URL as malicious with a score of 92, while the overall verdict was non‑malicious. OTX listed five pulses referencing the domain as of 2026-10-22. No external blocklists flagged the domain, but PhishDestroy’s internal blocklist marks it as suspicious as of 2026-10-22.

Infrastructure

The domain was registered with Cloudflare, Inc. on 2025-02-11 and expires on 2027-02-11. DNS resolved to Cloudflare IPs 104.21.66.124 (recorded in Canada) and 172.67.159.232, with corresponding AAAA records. The TLS certificate, issued by Google Trust Services, was valid from 2026-09-25 to 2026-12-24 and covers axonme.cc and *.axonme.cc; DNSSEC was not enabled.

What to do

Visitors should avoid entering credentials or downloading files from the site; if any information was submitted, change related passwords and monitor accounts for unusual activity. Defenders can block the domain at network perimeters, alert users, and review logs for connections to the recorded IP addresses. Add axonme.cc to internal threat‑intel feeds to ensure continued monitoring.

Useful links

urlscan.io scan and screenshotCloudflare Radar reportStored capture screenshotCloudflare Radar screenshot (2026-10-22T07:11:50Z)URLScan screenshot (2026-10-22T06:41:42Z)URLScan capture reportVirusTotal 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.

URLScan · 2026-10-22T06:37:10Z

Observed: · Retrieved:

Uuid
01a16253-d660-72dc-9f31-19d1954f0e44
Final url
https://axonme.cc/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://axonme.cc/",
        "from": "http://axonme.cc/",
        "status": 307
    }
]
Ip
104.21.66.124
Contacted domains
[
    "static.cloudflareinsights.com"
]
Contacted IP addresses
[
    "104.16.80.73",
    "104.21.66.124"
]
Asns
[
    "13335"
]
Document hash
f676a812569dc22eb0d5fc151593f2ea201a2131994cc9b0c67813fd91d243db
Script hashes
[
    "2595496fe48df6fcf9b1bc57c29a744c121eb4dd11566466bc13d2e52e6bbcc8"
]
Globals
[
    "__cfBeacon"
]
Tls
{
    "san": [
        "axonme.cc",
        "*.axonme.cc"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WE1",
    "subject": "axonme.cc",
    "protocol": "QUIC",
    "valid_to": "2026-12-24T04:26:35Z",
    "valid_from": "2026-09-25T03:28:03Z"
}
Domain age days
617
Apex age days
617
Tls age days
27
Tls valid days
90
Requests
7
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 92,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "cloudflare",
    "content-type": "text/html"
}
Cloudflare Radar · 2026-10-22T07:11:50Z

Observed: · Retrieved:

Uuid
e7644d37-f0c3-487b-8df7-83a9f971dd3c
Final url
https://axonme.cc/
Status
200
History
[
    {
        "url": "https://axonme.cc/",
        "status": 200
    }
]
DOM structure hash
d603ae7bfaa67ca48902185ba6e13fd72b52559178c00fd39beb5b403d53cb83
Document hash
54f26251007f742e396f1e3ea98f0eef2a3ed20aafb7378ff98b1bd8f21f6ebd
Domain risks
[
    "Information Technology",
    "Technology",
    "Business",
    "Business & Economy"
]
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "axonme.cc",
        "type": "A",
        "value": "104.21.66.124"
    },
    {
        "name": "axonme.cc",
        "type": "A",
        "value": "172.67.159.232"
    },
    {
        "name": "axonme.cc",
        "type": "AAAA",
        "value": "2606:4700:3034::6815:427c"
    },
    {
        "name": "axonme.cc",
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:9fe8"
    }
]
Dnssec valid
false
Ip
104.21.66.124
Registration record
{
    "registrar": "Cloudflare, Inc.",
    "created": "2025-02-11T09:25:58Z",
    "updated": "2026-02-12T08:05:19Z",
    "expires": "2027-02-11T09:25:58Z",
    "nameservers": [
        "cory.ns.cloudflare.com",
        "susan.ns.cloudflare.com"
    ]
}
VirusTotal · 2026-10-10T23:26:47Z

Observed: · Retrieved:

Vendor result counts
{
    "timeout": 0,
    "harmless": 46,
    "malicious": 14,
    "suspicious": 0,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "phishing",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Webroot": "malicious",
    "Fortinet": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "phishing",
    "BitDefender": "phishing",
    "Chong Lua Dao": "malicious",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "malicious"
}
Reputation
0
Categories
{
    "Sophos": "phishing and fraud",
    "Webroot": "Phishing and Other Frauds",
    "alphaMountain.ai": "Phishing (alphaMountain.ai)",
    "Forcepoint ThreatSeeker": "suspicious content"
}
Registrar
Cloudflare, Inc.
Created
2025-02-11T09:25:58Z
Expires
2027-02-11T09:25:58Z
Updated
2026-04-13T07:21:41Z
First seen
2025-02-11T10:35:01Z
DNS records
[
    {
        "ttl": 1800,
        "type": "SOA",
        "rname": "dns.cloudflare.com",
        "value": "cory.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "MX",
        "value": "_dc-mx.cee8a69de28d.axonme.cc",
        "priority": 0
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3034::6815:427c"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "cory.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "AAAA",
        "value": "2606:4700:3035::ac43:9fe8"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwhO4HBzY7LYa4kFN20xu2Lb6adDDOhlvB1+6IbgDKmA5vAQE87cvZz3KBsEeSoePmXDUs4AyFbtE7ZzoZRJDvrpW4G3ThaZ7dT8Lm/XPoB0sosoTgC2PKSlVahn4MYkBYDY9AEkRscWpH26BUbXaKofVAVWN5KcV58CzbObC1nLSg3xzAtNNWRREocmKXRhZu"
    },
    {
        "ttl": 3600,
        "type": "TXT",
        "value": "v=spf1 include:_spf.google.com include:spf.ymlp.com ~all"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "susan.ns.cloudflare.com"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "104.21.66.124"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "172.67.159.232"
    }
]
Dns at
2026-10-10T23:26:58Z
Jarm
27d40d40d00040d1dc42d43d00041d6183ff1bfae51ebd88d70384363d525c
Certificate
{
    "san": [
        "axonme.cc",
        "*.axonme.cc"
    ],
    "issuer": "Google Trust Services / WE1",
    "serial": "c564c479d4b264d71318734a991e082b",
    "sha256": "ac13a0a010c3f607f372e3583ea8b43a5d149d0aaa3cfbd81253c42047c99588",
    "subject": "axonme.cc",
    "valid_to": "2026-12-24T04:26:35Z",
    "valid_from": "2026-09-25T03:28:03Z"
}
Registration record
{
    "registrar": "Cloudflare, Inc.",
    "registrar_iana_id": "1910",
    "registrar_url": "http://www.cloudflare.com",
    "created": "2025-02-11T09:25:58Z",
    "updated": "2026-02-12T08:05:19Z",
    "expires": "2027-02-11T09:25:58Z",
    "status": [
        "clientTransferProhibited",
        "clienttransferprohibited"
    ],
    "nameservers": [
        "cory.ns.cloudflare.com",
        "susan.ns.cloudflare.com"
    ],
    "dnssec": "unsigned"
}
Registry data
{
    "status": [
        "client transfer prohibited"
    ],
    "events": {
        "expiration": "2027-02-11T09:25:58Z",
        "last changed": "2026-04-13T07:21:41Z",
        "registration": "2025-02-11T09:25:58Z",
        "last update of RDAP database": "2026-04-13T07:21:41Z"
    }
}
Website checks · 2026-10-22T07:12:24Z
Mail configuration
{
    "mx": [
        "_dc-mx.cee8a69de28d.axonme.cc"
    ],
    "spf": "v=spf1 include:_spf.google.com include:spf.ymlp.com ~all",
    "dmarc": true,
    "spf_lookups": 2
}
Caa records
{
    "domain": "axonme.cc"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Web archive observations
{
    "last": "2026-10-22T06:39:20Z",
    "first": "2025-03-24T12:24:46Z",
    "changes": 2,
    "days_archived": 3,
    "scans_per_day": 0,
    "avg_page_bytes": 1766
}
Page title and metadata
{
    "title": "Axon Middle East FZE"
}
Trackers
{
    "requests": 4
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 1,
        "tls": 18,
        "wait": 231,
        "connect": 7,
        "download": 1
    },
    "response_ms": 258
}
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
    ]
}
Carbon
{
    "bytes": 2298,
    "co2_grams": 0.0001,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "162.159.38.199",
            "host": "susan.ns.cloudflare.com"
        },
        {
            "ip": "108.162.193.93",
            "host": "cory.ns.cloudflare.com"
        }
    ],
    "zone": "axonme.cc"
}
Location
{
    "ip": "2606:4700:3035::ac43:9fe8",
    "asn": "13335",
    "org": "Cloudflare, Inc.",
    "city": "Toronto",
    "country": "CA"
}
Ssl
{
    "issuer": "Google Trust Services / WE1",
    "subject": "axonme.cc"
}
DNS records
{
    "A": [
        "172.67.159.232",
        "104.21.66.124"
    ],
    "MX": [
        "{\"exchange\": \"_dc-mx.cee8a69de28d.axonme.cc\", \"priority\": 0}"
    ],
    "NS": [
        "susan.ns.cloudflare.com",
        "cory.ns.cloudflare.com"
    ],
    "SOA": "{\"nsname\": \"cory.ns.cloudflare.com\", \"hostmaster\": \"dns.cloudflare.com\", \"serial\": 2415796214, \"refresh\": 10000, \"retry\": 2400, \"expire\": 604800, \"minttl\": 1800}",
    "TXT": [
        "v=spf1 include:_spf.google.com include:spf.ymlp.com ~all",
        "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAwhO4HBzY7LYa4kFN20xu2Lb6adDDOhlvB1+6IbgDKmA5vAQE87cvZz3KBsEeSoePmXDUs4AyFbtE7ZzoZRJDvrpW4G3ThaZ7dT8Lm/XPoB0sosoTgC2PKSlVahn4MYkBYDY9AEkRscWpH26BUbXaKofVAVWN5KcV58CzbObC1nLSg3xzAtNNWRREocmKXRhZu lX9UurwdC1ejYCC0UZulMxkuUlj8erIzi7NUU0k1gbzk"
    ],
    "AAAA": [
        "2606:4700:3035::ac43:9fe8",
        "2606:4700:3034::6815:427c"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Firewall
{
    "waf": "Cloudflare",
    "has_waf": true
}
Get ip
{
    "ip": "2606:4700:3035::ac43:9fe8",
    "family": 6
}
Redirects
{
    "chain": [
        "https://axonme.cc"
    ]
}
Subdomains
{
    "count": 1,
    "subdomains": [
        "mail.axonme.cc"
    ]
}
Tech stack
{
    "technologies": [
        "Cloudflare",
        "HTTP/3"
    ]
}
Page links
{
    "internal_count": 1
}
Registration record
{
    "registrar": "Cloudflare, Inc.",
    "created": "2025-02-11T09:25:58Z",
    "updated": "2026-02-12T08:05:19Z",
    "expires": "2027-02-11T09:25:58Z",
    "status": [
        "clientTransferProhibited https://icann.org/epp"
    ],
    "nameservers": [
        "cory.ns.cloudflare.com",
        "susan.ns.cloudflare.com"
    ]
}
HTTP headers
{
    "headers": {
        "server": "cloudflare",
        "content-type": "text/html"
    }
}

Questions about axonme.cc

Is axonme.cc legit?

No. PhishDestroy classifies axonme.cc as a phishing page (risk: critical, 100/100); it was first detected on 2026-10-22. VirusTotal: 14/92 engines flag it. Treat the site as unsafe.

Is axonme.cc safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on axonme.cc. 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 axonme.cc?

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 · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded2026-10-22 06:39 UTC
StateStored capture
HTTP status at archiveHTTP 200
Final URLhttp://axonme.cc/
Position1 / 4
Open capture Wayback Download

Domain details

Domain
IP Context Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
OTX tags 2026-10activeall-domainsblocklistcontentcryptodomainsdrainerfraudlivemonthlyphishdestroyphishingscam
Registrar Cloudflare US(US)
Abuse contact["registrar-abuse@cloudflare.com", "3432650ec337c945s@"]
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for axonme.cc →
RegistrationCreated Feb 11, 2025 — Expires Feb 11, 2027
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 22, 2026score 98/1001 brand signal
Submitted URLhttp://axonme.cc/
Favicon Hash
Observed page title
Axon Middle East FZE
Automated brand references
Across
TLS Certificate
Issued by Google Trust Services / WE1 · stored validity ends in 62 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
104.21.66.124
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
Toronto, CA
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Nameservers 2

  • cory.ns.cloudflare.com
  • susan.ns.cloudflare.com

Mail routing 1 MX record

  • _dc-mx.cee8a69de28d.axonme.ccpriority 0

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WE1
Valid from
2026-09-25 03:28:03
Valid until
2026-12-24 04:26:35
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection time
2026-10-22 07:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprintac13a0a010c3f607f372e3583ea8b43a5d149d0aaa3cfbd81253c42047c99588
Certificate names · 2 SANs
  • axonme.cc
  • *.axonme.cc

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

viewdns.info · 104.21.66.124rapiddns.io

Latest Classified Outcome 2026-10-22 11:01:54 UTC

Primary outcome Live content reason: Ordinary HTTP content served 90% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Content serving Content: Content served at root DNS: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-22 11:01:54 UTC
RDAP registration Unknown
Observed timeline last reachable: 2026-10-22 11:01:54 UTC last content: 2026-10-22 11:01:54 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.
Recorded subdomains1

Hostnames retained in the domain record or Certificate Transparency cache. A hostname alone does not establish current availability or malicious activity.

  • mail.axonme.ccDomain record

The original observation time is not recorded for these hostnames.

Technologies · 3 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

14 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
DNS8
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Lionic
Seclookup
Sophos
VIPRE
Webroot
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of axonme.cc · checked Oct 22, 2026

100
Good
Performance
FCP
0.77s
First Contentful Paint
LCP
1.35s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
0.79s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://axonme.cc/
Axon Middle East FZE
Response
HTTP 200
HTML body
2.6 KB
Compressed
1.4 KB
Links
1 internal · 0 external
Detected technologies
cloudflare
Selected response headers
Content-Type: text/html
Server: cloudflare
CF-Cache-Status: DYNAMIC
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: observed Cloaking flag: not observed
Saved response-header values · 14
alt-svc
h3=":443"; ma=86400
cf-cache-status
DYNAMIC
CF-RAY
a4e680bb5be5c923-IAD
Connection
keep-alive
Content-Encoding
gzip
Content-Type
text/html
Date
Thu, 22 Oct 2026 06:39:05 GMT
Last-Modified
Thu, 22 May 2025 06:47:27 GMT
Nel
{"report_to":"cf-nel","success_fraction":0.0,"max_age":604800}
Report-To
{"group":"cf-nel","max_age":604800,"endpoints":[{"url":"https://a.nel.cloudflare.com/report/v4?s=%2FX4%2FriISATjgMeH0S5LtwhnTrXSEnmSJifq7pB3Iwvs7vxeAaNX0vofYzG0zAnbBm3Ek2cqIjv4MqZ6weB1QkzoZ8MYTxLMmGcp0hFfSKdc75zh6ZQaxkQaXqtY%3D"}]}
Server
cloudflare
Server-Timing
cfCacheStatus;desc="DYNAMIC"
Transfer-Encoding
chunked
Vary
Accept-Encoding

Values retained by the collector; long values may be shortened during collection.

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history2

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→live_content

    content_served

  2. Availability monitor · First collection record

    Reachable

Recorded activity

5 entries
  1. AlienVault OTX

    5 community references

    View source
  2. Google Safe Browsing

    No threat flag

    View source
  3. VirusTotal

    14/92 engine detections

    View source
  4. Added to PhishDestroy

    axonme.cc

    View source
  5. URLScan

    Page captured

    View source

Check for cloaking

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

axonme.cc

Evidence & External Reports

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

4 evidence signal groups linked 0 stored notification records Last known active

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 axonme.cc)
  • 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/axonme.cc"
  title="PhishDestroy threat report for axonme.cc"
  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>