Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
claim-your-token.netlify.app favicon

claim-your-token.netlify.app

In short

PhishDestroy stores a record for claim-your-token.netlify.app. Source observations are dated separately; missing checks do not establish safety.

“EVM Token — $TOKEN Airdrop”

Review the evidence
Registrar
United StatesNetlify
Resolved IP
Germany63.176.8.218Amazon.com, Inc. · CDN
First observed
Oct 27, 2026
PhishDestroy assessment High
66/100
Evidence score
Availability Content unavailable Content was unavailable in the latest observation Observed HTTP probe
Risk signals
Stored blocklist matches: 2
VirusTotal
0 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLScan
Malicious
engine verdict · score 93
Page captures
2
open gallery
Oct 27, 2026 CDN
X Telegram API

Questions about claim-your-token.netlify.app

Is claim-your-token.netlify.app legit?

PhishDestroy stores a record for claim-your-token.netlify.app. Source observations are dated separately; missing checks do not establish safety.

Is claim-your-token.netlify.app safe to connect a wallet?

This report does not record which wallet requests claim-your-token.netlify.app 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 claim-your-token.netlify.app?

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

Source evidenceVirusTotal 0 / 92 6 sources

URLScan

Malicious · engine verdict · score 93

SHA-256 2a1cbe9edd41c5765ac83afb0f1831741aa2b6550c7eeda04e175cc8be39a841

Open report
URLScanOriginal source recordObserved: 23 fields

Observed: · Retrieved:

Report ID

01a17e47-6a63-7619-87f3-d30d1ee7b43b

Final URL

https://claim-your-token.netlify.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://claim-your-token.netlify.app/
    From
    http://claim-your-token.netlify.app/
    Status
    307

IP address

35.157.26.135

Reverse DNS (PTR)

ec2-35-157-26-135.eu-central-1.compute.amazonaws.com

Contacted domains

  • www.google.com
  • bsc-dataseed2.bnbchain.org
  • bsc-dataseed1.bnbchain.org
  • bsc.blockrazor.xyz
  • t1.gstatic.com
  • bsc-rpc.publicnode.com
  • api.dicebear.com
  • zen-video-arrest-monster.xyz
  • t2.gstatic.com
  • dns.google
  • cloudflare-dns.com
  • t0.gstatic.com
  • t3.gstatic.com

Contacted IP addresses

  • 185.111.111.155
  • 188.114.96.3
  • 142.251.20.103
  • 142.251.14.147
  • 142.251.110.103
  • 142.250.154.105
  • 142.251.152.119
  • 34.251.166.204
  • 63.35.242.38
  • 8.8.8.8
  • 104.16.248.249
  • 172.67.72.107
  • 104.20.24.117
  • 35.157.26.135

Autonomous systems (ASN)

  • 212238
  • 13335
  • 15169
  • 16509

Server countries

  • DE
  • US
  • IE

Document hash

61d677745d0fff893d7b80e68599501bd79169ba317468313e91d176df33aaaf

Script hashes

  • e4d4461708845b520f564e0ba37df8520bc5a6edde9a1abe65d372d0558744fd

JavaScript globals

  • _0x412c
  • _0x4a00
  • openModal
  • __PROXY__

Browser storage keys

  • __c2

TLS session and certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Cipher
AES_128_GCM
Issuer
DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.netlify.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

0

Registered domain age, days

2831

Certificate age, days

253

Certificate validity, days

396

Page requests

38

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
93
Malicious
Yes
Overall verdict
Score
0
Malicious
No

HTTP headers

Server
Netlify
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a17e47-6a63-7619-87f3-d30d1ee7b43b
Final url
https://claim-your-token.netlify.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://claim-your-token.netlify.app/",
        "from": "http://claim-your-token.netlify.app/",
        "status": 307
    }
]
Ip
35.157.26.135
Ptr
ec2-35-157-26-135.eu-central-1.compute.amazonaws.com
Contacted domains
[
    "www.google.com",
    "bsc-dataseed2.bnbchain.org",
    "bsc-dataseed1.bnbchain.org",
    "bsc.blockrazor.xyz",
    "t1.gstatic.com",
    "bsc-rpc.publicnode.com",
    "api.dicebear.com",
    "zen-video-arrest-monster.xyz",
    "t2.gstatic.com",
    "dns.google",
    "cloudflare-dns.com",
    "t0.gstatic.com",
    "t3.gstatic.com"
]
Contacted IP addresses
[
    "185.111.111.155",
    "188.114.96.3",
    "142.251.20.103",
    "142.251.14.147",
    "142.251.110.103",
    "142.250.154.105",
    "142.251.152.119",
    "34.251.166.204",
    "63.35.242.38",
    "8.8.8.8",
    "104.16.248.249",
    "172.67.72.107",
    "104.20.24.117",
    "35.157.26.135"
]
Asns
[
    "212238",
    "13335",
    "15169",
    "16509"
]
Countries
[
    "DE",
    "US",
    "IE"
]
Document hash
61d677745d0fff893d7b80e68599501bd79169ba317468313e91d176df33aaaf
Script hashes
[
    "e4d4461708845b520f564e0ba37df8520bc5a6edde9a1abe65d372d0558744fd"
]
Globals
[
    "_0x412c",
    "_0x4a00",
    "openModal",
    "__PROXY__"
]
Storage keys
[
    "__c2"
]
Tls
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app",
    "protocol": "TLS 1.3",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Domain age days
0
Apex age days
2831
Tls age days
253
Tls valid days
396
Requests
38
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 93,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Netlify",
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
}
Separate monitor record · 2026-10-29 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a17e47-6a63-7619-87f3-d30d1ee7b43b
score
0
malicious
false
result_at
2026-10-29T04:30:40Z
enriched_at
2026-10-28T09:17:18Z
source_timestamps
{"urlscan_result_at":"2026-10-29 05:30:40","urlscan_enriched_at":"2026-10-28 10:17:18"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 12 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
56
Malicious
0
Suspicious
0
Undetected
36

Reputation score

0

Registrar

Name.com, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    120
    Type
    A
    Value
    18.208.88.157
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::259
  • TTL, seconds
    120
    Type
    A
    Value
    98.84.224.111
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::258

DNS records observed

JARM fingerprint

40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319

Certificate

Subject alternative names
  • *.netlify.app
  • netlify.app
Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Serial
cd5d0afb0611b5bd9d692535c0ca7c4
SHA-256
bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Subject
*.netlify.app
Valid until
Valid from

Registration record

Registrar
Name.com, Inc.
Registrar IANA ID
625
Registrar URL
http://www.name.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
Nameservers
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 36
}
Reputation
0
Registrar
Name.com, Inc.
Created
2018-05-08T22:48:05Z
Expires
2025-05-08T22:48:05Z
Updated
2024-04-11T16:00:14Z
First seen
2026-10-27T06:49:46Z
DNS records
[
    {
        "ttl": 120,
        "type": "A",
        "value": "18.208.88.157"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::259"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "98.84.224.111"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::258"
    }
]
Dns at
2026-10-27T06:49:48Z
Jarm
40d40d40d00000000043d43d00043d6aff5ab0f4fc31897186312c9e639319
Certificate
{
    "san": [
        "*.netlify.app",
        "netlify.app"
    ],
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "serial": "cd5d0afb0611b5bd9d692535c0ca7c4",
    "sha256": "bc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478",
    "subject": "*.netlify.app",
    "valid_to": "2027-03-19T23:59:59Z",
    "valid_from": "2026-02-16T00:00:00Z"
}
Registration record
{
    "registrar": "Name.com, Inc.",
    "registrar_iana_id": "625",
    "registrar_url": "http://www.name.com",
    "created": "2018-05-08T22:48:05Z",
    "updated": "2024-04-11T16:00:14Z",
    "expires": "2025-05-08T22:48:05Z",
    "status": [
        "clientTransferProhibited"
    ],
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ],
    "dnssec": "unsigned"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-27 06:49:25 UTC

The summary above and this provider record were collected at different times. Both remain available; malicious and suspicious classifications are shown separately.

record_source
collected_observations.vt
analysis_at
2026-10-27T06:49:25Z
fetched_at
2026-10-27T17:12:58Z
stats
{"timeout":0,"harmless":56,"malicious":0,"suspicious":0,"undetected":36}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

15 / 100 · heuristic score · 7 brand references · 1 classification

Open report
Separate monitor score · 15 / 100 · 2026-10-27T19:20:13Z

This dated monitor analysis is separate from the primary PhishDestroy analysis above. A heuristic score is not a measured probability.

record_source
domain_monitor.dom_analysis
heuristic_score
15
analyzed_at
2026-10-27T19:20:13Z
source_timestamp
2026-10-27 20:20:13
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

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: 20 fields

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
netlify.app
Allowed issuers
  • digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Open Graph URL
https://claim-your-token.netlify.app/
Page title
EVM Token — $TOKEN Airdrop
Open Graph type
website
Open Graph image
https://claim-your-token.netlify.app/og-base.png
Open Graph title
EVM Token — $TOKEN Airdrop
Description
EVM Token · Claim the $TOKEN airdrop and explore the latest EVM token information.
Twitter card
summary_large_image
Open Graph description
EVM Token · Claim the $TOKEN airdrop and explore the latest EVM token information.

Trackers

Requests
24
Observed services
  • Name
    Google
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    7
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    7

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
2
TLS
9
Waiting
25
Connection
8
Download
25
Response time, ms
69

TLS connection

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

Ports

Open ports
  • 80
  • 443

Carbon estimate

Bytes
43591
CO₂, grams
0.0016
Cleaner than, %
40

DNS servers

Nameservers
  • IP address
    198.51.45.1
    Host
    dns2.p01.nsone.net
  • IP address
    198.51.44.65
    Host
    dns3.p01.nsone.net
  • IP address
    198.51.45.65
    Host
    dns4.p01.nsone.net
  • IP address
    198.51.44.1
    Host
    dns1.p01.nsone.net
DNS zone
netlify.app

Location

IP address
2a05:d014:58f:6200::259
ASN
16509
Organization
Amazon.com, Inc.
City
Frankfurt
Country
DE

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Subject
*.netlify.app

DNS records

A
  • 63.176.8.218
  • 35.157.26.135
AAAA
  • 2a05:d014:58f:6200::259
  • 2a05:d014:58f:6200::258

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=31536000; includeSubDomains; preload
Observation
Site is compatible with the HSTS preload list!
Preload compatible
Yes

HTTP security policies

X-Frame-Options
No
Referrer-Policy
No
X-XSS-Protection
No
Permissions-Policy
No
X-Content-Type-Options
No
Content-Security-Policy
No
Strict-Transport-Security
max-age=31536000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
2a05:d014:58f:6200::258
IP version
6

Redirects

Redirect chain
  • https://claim-your-token.netlify.app

HTTP headers

Response headers
Server
Netlify
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31536000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "netlify.app",
    "issuers": [
        "digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "ogUrl": "https://claim-your-token.netlify.app/",
    "title": "EVM Token — $TOKEN Airdrop",
    "ogType": "website",
    "ogImage": "https://claim-your-token.netlify.app/og-base.png",
    "ogTitle": "EVM Token — $TOKEN Airdrop",
    "description": "EVM Token · Claim the $TOKEN airdrop and explore the latest EVM token information.",
    "twitterCard": "summary_large_image",
    "ogDescription": "EVM Token · Claim the $TOKEN airdrop and explore the latest EVM token information."
}
Trackers
{
    "requests": 24,
    "trackers": [
        {
            "name": "Google",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 7
        },
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 7
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 2,
        "tls": 9,
        "wait": 25,
        "connect": 8,
        "download": 25
    },
    "response_ms": 69
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_128_GCM_SHA256",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80,
        443
    ]
}
Carbon
{
    "bytes": 43591,
    "co2_grams": 0.0016,
    "cleaner_than": 40
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.45.1",
            "host": "dns2.p01.nsone.net"
        },
        {
            "ip": "198.51.44.65",
            "host": "dns3.p01.nsone.net"
        },
        {
            "ip": "198.51.45.65",
            "host": "dns4.p01.nsone.net"
        },
        {
            "ip": "198.51.44.1",
            "host": "dns1.p01.nsone.net"
        }
    ],
    "zone": "netlify.app"
}
Location
{
    "ip": "2a05:d014:58f:6200::259",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "city": "Frankfurt",
    "country": "DE"
}
Ssl
{
    "issuer": "DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1",
    "subject": "*.netlify.app"
}
DNS records
{
    "A": [
        "63.176.8.218",
        "35.157.26.135"
    ],
    "AAAA": [
        "2a05:d014:58f:6200::259",
        "2a05:d014:58f:6200::258"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31536000; includeSubDomains; preload",
    "message": "Site is compatible with the HSTS preload list!",
    "compatible": true
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": "max-age=31536000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2a05:d014:58f:6200::258",
    "family": 6
}
Redirects
{
    "chain": [
        "https://claim-your-token.netlify.app"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Netlify",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
    }
}
Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Checked, no match

Last checked

Stored Capture · 2 captures

Primary capture 1 / 2
SourcePrimary capture
Recorded
StateStored capture
Position1 / 2
Open capture Wayback Download
All capture links and hashes (2)
claim-your-token.netlify.app: Crypto scam — Blocked by MetaMask, flagged by SEAL, 3/92 VirusTotal engines. PhishDestroy risk score 66/100 (high).
Social preview card claim-your-token.netlify.app: Crypto scam — Blocked by MetaMask, flagged by SEAL, 3/92 VirusTotal engines. PhishDestroy risk score 66/100 (high). v d90ad62ecccd

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 93 report ↗
IP Context Germany63.176.8.218 Netlify shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Netlify US(US)
Abuse contactabuse@netlify.com
Hosting abuse contact abuse@netlify.com Amazon.com, Inc. · AS16509
HTTP Status404 Not Found
Technical detailsProvenance & timestamps
First DetectedOct 27, 2026
DOM Analysisanalyzed Oct 27, 2026score 15/1007 brand signals
Submitted URLhttp://claim-your-token.netlify.app/
Favicon Hash
Observed page title
EVM Token — $TOKEN Airdrop
Automated brand references
Arbitrum Base Chainlink Ethereum Optimism Polygon Uniswap
TLS Certificate
Issued by DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1 · stored validity ends in 140 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
Germany63.176.8.218
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Amazon.com, Inc.
Observed location
GermanyFrankfurt, DE
Server header
Netlify

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
DigiCert Inc / DigiCert Global G2 TLS RSA SHA256 2020 CA1
Valid from
2026-02-16 00:00:00
Valid until
2027-03-19 23:59:59
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-27 17:02:05 UTC
Collection source
PhishDestroy collector
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Certificate names · 1 SAN
  • netlify.app

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

viewdns.info · 63.176.8.218rapiddns.io

Latest Classified Outcome 2026-10-30 11:05:38 UTC

No phishing content was served at the latest check.

Technical details
Primary outcome Inactive reason: Http No Content 70% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Root path has no content Content: Absent At Root DNS: Stale Registration: Unknown
Latest HTTP observation Inactive Http No Content 70% 2026-10-30 11:05:38 UTC
RDAP registration
Observed timeline last reachable: 2026-10-28 00:30:50 UTC last content: 2026-10-28 00:30:50 UTC current episode first observed: 2026-10-28 12:13:25 UTC observed RIP window: 2026-10-28 00:30:50 UTC → 2026-10-28 12:13:25 UTC · 11.71h midpoint estimate ≈ 2026-10-28 06:22:07 UTC · precision medium · basis bounded
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
Registration & observation details9

Availability observations

Last reachable observation
Last content observation
Outcome first observed
Observation window starts
Observation window ends
Estimated change time
Observation window · hours
11.71
Estimate basis
Bounded by observations
Estimate precision
Medium

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: 38 SHA-256 hashes: 24 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-10-29 01:54 UTC.

Open this scan on URLScan 01a17e47-6a63-7619-87f3-d30d1ee7b43b ↗

Stored observation history3

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

    live_content→inactive

    http_no_content

  2. Availability monitor · Recorded state

    live_content

    content_served

  3. Domain monitor · First collection record

    Reachable

All retained availability observations14

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_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:05:38.000000
    Evidence SHA-256
    42b4ec3a82fa0b5a6ed85f938bdfc1d6bda640863186d83ddd0f00edc4739a9d
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 12:05:38
    Evidence reason
    http_other
  2. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:05:38.000000
    Evidence SHA-256
    42b4ec3a82fa0b5a6ed85f938bdfc1d6bda640863186d83ddd0f00edc4739a9d
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 12:05:38
    Evidence reason
    http_other
  3. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:05:59.000000
    Evidence SHA-256
    226a8e995e3515d7fa5d1eb04b672af725875e7ae8b7844984df0a7e0e91c3d6
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 00:05:59
    Evidence reason
    http_other
  4. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:05:59.000000
    Evidence SHA-256
    226a8e995e3515d7fa5d1eb04b672af725875e7ae8b7844984df0a7e0e91c3d6
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-30 00:05:59
    Evidence reason
    http_other
  5. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:06:21.000000
    Evidence SHA-256
    0cb46d3fc977d81af554c6c257b185e0b07cb966ba4f4f65405f1ecc589b2317
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 12:06:21
    Evidence reason
    http_other
  6. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:06:21.000000
    Evidence SHA-256
    0cb46d3fc977d81af554c6c257b185e0b07cb966ba4f4f65405f1ecc589b2317
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 12:06:21
    Evidence reason
    http_other
  7. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:05:45.000000
    Evidence SHA-256
    35613e493a2911fa46aa69a3b43327a601c15a05fc5003e74a1555f7e765496f
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 01:05:45
    Evidence reason
    http_other
  8. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 01:05:45.000000
    Evidence SHA-256
    35613e493a2911fa46aa69a3b43327a601c15a05fc5003e74a1555f7e765496f
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-29 01:05:45
    Evidence reason
    http_other
  9. current_http_probeinactive
    Observation source
    current_http_probe
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    stale
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 13:13:25.000000
    Evidence SHA-256
    b78207785d70cb20cd08bb63f4ec998485ecee804387882be9eedc7fed5b388e
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 13:13:25
    Evidence reason
    http_other
  10. http_observationinactive
    Observation source
    http_observation
    Cause
    http_no_content
    Availability state
    root_no_content
    Content state
    absent_at_root
    DNS state
    unknown
    Recorded HTTP status
    404
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    70
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 13:13:25.000000
    Evidence SHA-256
    b78207785d70cb20cd08bb63f4ec998485ecee804387882be9eedc7fed5b388e
    HTTP probe value as recorded
    404
    Evidence timestamp as recorded
    2026-10-28 13:13:25
    Evidence reason
    http_other
  11. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 01:30:50.000000
    Evidence SHA-256
    47396db6a7aec4aa31ce17da0ed1335b4aa4a9c29969c5af4a3e968f08bc7675
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:30:50
    Evidence reason
    alive_content
  12. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 01:30:50.000000
    Evidence SHA-256
    47396db6a7aec4aa31ce17da0ed1335b4aa4a9c29969c5af4a3e968f08bc7675
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 01:30:50
    Evidence reason
    alive_content
  13. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 17:54:21.000000
    Evidence SHA-256
    17c2e9676c415dcce521118e6f9d725b85c1f1819a2c8fb8cb5396f4d5527403
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 17:54:21
    Evidence reason
  14. http_observationunknown
    Observation source
    http_observation
    Cause
    http_2xx_unclassified
    Availability state
    unknown
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    40
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 17:54:21.000000
    Evidence SHA-256
    17c2e9676c415dcce521118e6f9d725b85c1f1819a2c8fb8cb5396f4d5527403
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 17:54:21
    Evidence reason

Threat Response Pipeline

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

Recorded events: 9. 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
    claim-your-token.netlify.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Blocklist Detection · Automated brand label: Arbitrum · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 6 of 6
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 93
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Automated brand label: Arbitrum
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · Content Observed Unavailable Recorded: 2 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Content Observed Unavailable
    The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.

Recorded activity

3 entries
  1. Added to PhishDestroy

    claim-your-token.netlify.app

    View source
  2. URLScan

    Page captured

    View source
  3. VirusTotal

    0/92 engine detections

    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

Lookalike domains

28 stored lookalike domains

a.rbitrum.io subdomain A 188.114.96.3 abitrum.io omission A 188.114.96.3NS hank.ns.cloudflare.com abritrum.io transposition A 188.114.96.3NS hank.ns.cloudflare.com arbbitrum.io repetition A 185.53.179.128NS ns1.dyna-ns.net arbiitrum.io repetition A 185.53.179.128NS ns1.dyna-ns.net arbirtum.io transposition A 188.114.96.3NS hank.ns.cloudflare.com arbirum.io omission A 199.91.220.73NS ns1.dnsowl.com arbit.rum.io subdomain A 13.248.169.48NS ns1.afternic.com arbitr.um.io subdomain A 3.139.159.151 arbitram.io vowel-swap A 77.247.179.86NS ns1.badgerdns.com arbitrium.io insertion A 88.212.204.58MX mx.yandex.netNS c.ns.over.ru arbitrm.io omission A 104.21.28.233NS hank.ns.cloudflare.com
Show all (16)
arbitrmu.io transposition A 185.53.179.128NS ns1.dyna-ns.net arbitru.io omission A 104.21.2.146NS hank.ns.cloudflare.com arbitruum.io repetition A 185.53.179.128NS ns1.dyna-ns.net arbittrum.io insertion A 185.53.179.128NS ns1.dyna-ns.net arbitum.io omission A 104.21.95.219NS hank.ns.cloudflare.com arbiturm.io transposition A 185.53.179.128NS ns1.dyna-ns.net arbtirum.io transposition A 185.53.179.128NS ns1.dyna-ns.net arbtrum.io omission A 188.114.96.3NS hank.ns.cloudflare.com aribtrum.io transposition A 199.91.220.73NS ns1.dnsowl.com aritrum.io omission A 188.114.96.3NS hank.ns.cloudflare.com rabitrum.io transposition A 185.53.179.128NS ns1.dyna-ns.net rbitrum.io omission A 188.114.96.3NS hank.ns.cloudflare.com arbitrrum.io insertion A 104.21.56.168NS hank.ns.cloudflare.com arbitrumm.io addition A 185.53.179.128NS ns1.dyna-ns.net arbitrun.io homoglyph A 104.21.88.223NS hank.ns.cloudflare.com xn--rbitrum-r3a.io homoglyph A 104.21.60.23NS dalary.ns.cloudflare.com

Check for cloaking

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

claim-your-token.netlify.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal ChainPatrol URLQuery SSL Labs Certificate hostname mismatch 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?

2 evidence signal groups linked Content unavailable
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 claim-your-token.netlify.app)
  • 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/claim-your-token.netlify.app"
  title="PhishDestroy threat report for claim-your-token.netlify.app"
  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>