Skip to security report
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
drop-token.netlify.app favicon

drop-token.netlify.app

In short

PhishDestroy records drop-token.netlify.app as a captured page titled EVM Token — $TOKEN Airdrop, presenting a wallet-connection claim interface.

“EVM Token — $TOKEN Airdrop”

Registrar
United StatesNetlify
Resolved IP
Germany63.176.8.218Amazon.com, Inc. · CDN
First observed
Oct 29, 2026
PhishDestroy assessment High
66/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Stored blocklist matches: 2
VirusTotal
engine detections ·
Blocklist matches
MetaMask, SEAL
URLScan
engine verdict · score 99
Page captures
open gallery
Oct 29, 2026 CDN
X Telegram API

Analysis

Domain summary

PhishDestroy records drop-token.netlify.app as a captured page titled EVM Token — $TOKEN Airdrop, presenting a wallet-connection claim interface.

High
Status
Last known active
VirusTotal
0 / 92
Blocklist matches
2
Scam type (automated label)
Crypto Drainer
Hosting
Germany63.176.8.218Amazon.com, Inc. · CDN
Registrar
United StatesNetlify
Page captures
3

PhishDestroy analysis, reviewed version

The captured drop-token.netlify.app page presents an EVM Token airdrop interface with the headline "Claim the $TOKEN airdrop now." Its main interaction is a "Connect Wallet — Access the airdrop" button inside an "Airdrop Access" panel, alongside a strip of network and protocol names, a market data section whose price, market cap, liquidity and volume fields show em-dash placeholders, and panels listing airdrop overview figures (61,000 claims, 39,000 distribution) and token information rows.

On VirusTotal, the stored result for the domain drop-token.netlify.app reports 0 detections out of 92 engines, with 0 malicious and 0 suspicious verdicts. No vendor flagged the domain in that result, so there are no specific vendor verdicts to report for this case.

Source evidenceVirusTotal 0 / 92 8 sources

URLScan

Malicious · engine verdict · score 99

SHA-256 a1531c92793b450ff24b0d9bcba71a967576846e0e8004fbe02b8620d81e8eb1

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a187f8-253f-724e-9688-61fdee7a8596

Final URL

https://drop-token.netlify.app/

HTTP response

200

IP address

18.208.88.157

Reverse DNS (PTR)

ec2-18-208-88-157.compute-1.amazonaws.com

Contacted domains

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

Contacted IP addresses

  • 79.127.243.187
  • 142.251.167.104
  • 142.250.72.4
  • 142.250.190.228
  • 142.250.217.132
  • 142.251.156.119
  • 104.21.63.172
  • 98.90.255.107
  • 50.16.112.207
  • 104.26.8.35
  • 104.20.24.117
  • 8.8.4.4
  • 104.16.249.249
  • 18.208.88.157

Autonomous systems (ASN)

  • 60068
  • 15169
  • 13335
  • 14618

Server countries

  • US

Document hash

09bbe444f849bf115dd84f0a2d457ee60a406cf1d253446a6f24c9d2f25875b8

Script hashes

  • e4d4461708845b520f564e0ba37df8520bc5a6edde9a1abe65d372d0558744fd

JavaScript globals

  • _0x412c
  • _0x4a00
  • __PROXY__
  • openModal
  • vmp_59b280
  • __S1RESULT__

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

0

Certificate age, days

255

Certificate validity, days

396

Page requests

24

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
99
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
01a187f8-253f-724e-9688-61fdee7a8596
Final url
https://drop-token.netlify.app/
Status
200
Ip
18.208.88.157
Ptr
ec2-18-208-88-157.compute-1.amazonaws.com
Contacted domains
[
    "www.google.com",
    "t3.gstatic.com",
    "t1.gstatic.com",
    "zen-castle-depth-gas.xyz",
    "bsc-dataseed2.bnbchain.org",
    "bsc-dataseed1.bnbchain.org",
    "bsc.blockrazor.xyz",
    "bsc-rpc.publicnode.com",
    "api.dicebear.com",
    "t0.gstatic.com",
    "t2.gstatic.com",
    "dns.google",
    "cloudflare-dns.com"
]
Contacted IP addresses
[
    "79.127.243.187",
    "142.251.167.104",
    "142.250.72.4",
    "142.250.190.228",
    "142.250.217.132",
    "142.251.156.119",
    "104.21.63.172",
    "98.90.255.107",
    "50.16.112.207",
    "104.26.8.35",
    "104.20.24.117",
    "8.8.4.4",
    "104.16.249.249",
    "18.208.88.157"
]
Asns
[
    "60068",
    "15169",
    "13335",
    "14618"
]
Countries
[
    "US"
]
Document hash
09bbe444f849bf115dd84f0a2d457ee60a406cf1d253446a6f24c9d2f25875b8
Script hashes
[
    "e4d4461708845b520f564e0ba37df8520bc5a6edde9a1abe65d372d0558744fd"
]
Globals
[
    "_0x412c",
    "_0x4a00",
    "__PROXY__",
    "openModal",
    "vmp_59b280",
    "__S1RESULT__"
]
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
0
Tls age days
255
Tls valid days
396
Requests
24
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "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-30 04:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a187f8-253f-724e-9688-61fdee7a8596
score
0
malicious
false
result_at
2026-10-30T04:30:24Z
enriched_at
2026-10-30T09:11:43Z
source_timestamps
{"urlscan_result_at":"2026-10-30 05:30:24","urlscan_enriched_at":"2026-10-30 10:11:43"}
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
0
Malicious
0
Suspicious
0
Undetected
92

Reputation score

0

Registrar

Name.com, Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    120
    Type
    A
    Value
    98.84.224.111
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::259
  • TTL, seconds
    120
    Type
    A
    Value
    18.208.88.157
  • 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": 0,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 92
}
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-29T14:00:44Z
DNS records
[
    {
        "ttl": 120,
        "type": "A",
        "value": "98.84.224.111"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::259"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "18.208.88.157"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::258"
    }
]
Dns at
2026-10-29T15:02: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-29 14:57:32 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-29T14:57:32Z
fetched_at
2026-10-29T19:42:18Z
stats
{"timeout":0,"harmless":0,"malicious":0,"suspicious":0,"undetected":92}

OTX

no community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 11 fields

Observed: · Retrieved:

Report ID

426f27e5-ad0f-43c5-b05a-8dbc9541e73b

Final URL

https://drop-token.netlify.app/

HTTP response

200

Navigation history

  • URL
    https://drop-token.netlify.app/
    Status
    200

DOM structure hash

d7565a9f578372b758a4f56c95ba53661c20c7c1f13fc044f47a4154e821b636

Document hash

176ca6ddaba7780b203053377ad3bb75f1d7a4badfa0ee8c671d8be14242b437

Cloudflare Radar rank

Rank range
>200000

DNS records

  • Name
    drop-token.netlify.app
    Type
    A
    Value
    63.176.8.218
  • Name
    drop-token.netlify.app
    Type
    A
    Value
    35.157.26.135
  • Name
    drop-token.netlify.app
    Type
    AAAA
    Value
    2a05:d014:58f:6200::258
  • Name
    drop-token.netlify.app
    Type
    AAAA
    Value
    2a05:d014:58f:6200::259

DNSSEC valid

No

IP address

127.0.1.13

127.0.1.13 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record

Registrar
Name.com, Inc.
Registered
Updated
Expires
Nameservers
  • dns1.p01.nsone.net
  • dns2.p01.nsone.net
  • dns3.p01.nsone.net
  • dns4.p01.nsone.net
Original source fields · JSON
Uuid
426f27e5-ad0f-43c5-b05a-8dbc9541e73b
Final url
https://drop-token.netlify.app/
Status
200
History
[
    {
        "url": "https://drop-token.netlify.app/",
        "status": 200
    }
]
DOM structure hash
d7565a9f578372b758a4f56c95ba53661c20c7c1f13fc044f47a4154e821b636
Document hash
176ca6ddaba7780b203053377ad3bb75f1d7a4badfa0ee8c671d8be14242b437
Radar rank
{
    "bucket": ">200000"
}
DNS records
[
    {
        "name": "drop-token.netlify.app",
        "type": "A",
        "value": "63.176.8.218"
    },
    {
        "name": "drop-token.netlify.app",
        "type": "A",
        "value": "35.157.26.135"
    },
    {
        "name": "drop-token.netlify.app",
        "type": "AAAA",
        "value": "2a05:d014:58f:6200::258"
    },
    {
        "name": "drop-token.netlify.app",
        "type": "AAAA",
        "value": "2a05:d014:58f:6200::259"
    }
]
Dnssec valid
false
Ip
127.0.1.13

127.0.1.13 is not a public internet address. It is the value stored in this source record, not the site's hosting address.

Registration record
{
    "registrar": "Name.com, Inc.",
    "created": "2018-05-08T22:48:05Z",
    "updated": "2026-06-22T22:48:05Z",
    "expires": "2031-05-08T22:48:05Z",
    "nameservers": [
        "dns1.p01.nsone.net",
        "dns2.p01.nsone.net",
        "dns3.p01.nsone.net",
        "dns4.p01.nsone.net"
    ]
}

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-29T15:20:14Z

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-29T15:20:14Z
source_timestamp
2026-10-29 16:20:14
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

The narrative generation date is separate from observation dates. These are the retained publication fields, not an additional independent detection.

ai_title
drop-token.netlify.app — EVM Token $TOKEN Airdrop Claim Page
ai_description
PhishDestroy records drop-token.netlify.app as a captured page titled EVM Token — $TOKEN Airdrop, presenting a wallet-connection claim interface.
ai_summary
The captured drop-token.netlify.app page presents an EVM Token airdrop interface with the headline "Claim the $TOKEN airdrop now." Its main interaction is a "Connect Wallet — Access the airdrop" button inside an "Airdrop Access" panel, alongside a strip of network and protocol names, a market data section whose price, market cap, liquidity and volume fields show em-dash placeholders, and panels listing airdrop overview figures (61,000 claims, 39,000 distribution) and token information rows. On VirusTotal, the stored result for the domain drop-token.netlify.app reports 0 detections out of 92 engines, with 0 malicious and 0 suspicious verdicts. No vendor flagged the domain in that result, so there are no specific vendor verdicts to report for this case.
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-29 20:46:49
revision
4e3a86a7181899be9f48432b43774a97e8a49c897831de70ab6a233f3b463cf0
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

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
3
Domain
netlify.app
Allowed issuers
  • amazon.com
  • digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Page title and metadata

Open Graph URL
https://drop-token.netlify.app/
Page title
EVM Token — $TOKEN Airdrop
Open Graph type
website
Open Graph image
https://drop-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
23
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
4
TLS
9
Waiting
574
Connection
8
Download
13
Response time, ms
608

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
43567
CO₂, grams
0.0016
Cleaner than, %
40

DNS servers

Nameservers
  • IP address
    198.51.44.1
    Host
    dns1.p01.nsone.net
  • 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
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
  • 35.157.26.135
  • 63.176.8.218
AAAA
  • 2a05:d014:58f:6200::258
  • 2a05:d014:58f:6200::259

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::259
IP version
6

Redirects

Redirect chain
  • https://drop-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": 3,
    "domain": "netlify.app",
    "issuers": [
        "amazon.com",
        "digicert.com;account=2d83e9ac9b6776c3f215150f6ebceea8cefe3bc2e1fb5efffb1d71e200575226"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Page title and metadata
{
    "ogUrl": "https://drop-token.netlify.app/",
    "title": "EVM Token — $TOKEN Airdrop",
    "ogType": "website",
    "ogImage": "https://drop-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": 23,
    "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": 4,
        "tls": 9,
        "wait": 574,
        "connect": 8,
        "download": 13
    },
    "response_ms": 608
}
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": 43567,
    "co2_grams": 0.0016,
    "cleaner_than": 40
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.44.1",
            "host": "dns1.p01.nsone.net"
        },
        {
            "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"
        }
    ],
    "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": [
        "35.157.26.135",
        "63.176.8.218"
    ],
    "AAAA": [
        "2a05:d014:58f:6200::258",
        "2a05:d014:58f:6200::259"
    ]
}
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::259",
    "family": 6
}
Redirects
{
    "chain": [
        "https://drop-token.netlify.app"
    ]
}
HTTP headers
{
    "headers": {
        "server": "Netlify",
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31536000; includeSubDomains; preload"
    }
}

Questions about drop-token.netlify.app

Is drop-token.netlify.app legit?

PhishDestroy records drop-token.netlify.app as a captured page titled EVM Token — $TOKEN Airdrop, presenting a wallet-connection claim interface.

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

This report does not record which wallet requests drop-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 drop-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

Extracted from stored page analysis

Observed indicators

1 wallet · 0 Telegram

Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.

ETH
0xa490080534690F6C9e488CE808e99cCB8eBC68a6Format validated · Domain analysis

IoC extraction recorded 2026-10-30 05:00:16 UTC

Blocklist matchesMetaMask · PhishDestroy · SEAL · no match in the other 9 3
MetaMask Listed View source
PhishDestroy PhishDestroy list View source
SEAL Listed View source

Last checked

Stored Capture · 3 captures

All capture links and hashes (3)
drop-token.netlify.app: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 66/100 (high).
Social preview card drop-token.netlify.app: Crypto scam — Blocked by MetaMask, flagged by SEAL. PhishDestroy risk score 66/100 (high). v 0fd4464ab98e

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 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 Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 29, 2026
DOM Analysisanalyzed Oct 29, 2026score 15/1007 brand signals
IoC Extractionscanned Oct 30, 20261 wallet · 0 Telegram IoC
Submitted URLhttps://drop-token.netlify.app/?… query redacted
Favicon Hash
Observed page title
EVM Token — $TOKEN Airdrop
Automated brand references
Arbitrum Base Chainlink Ethereum Optimism Polygon Uniswap
TLS Certificate
Issued by 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
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 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
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintbc3a8134c21a842e64ea34d488826dd2ba50f59a3bcbaed1e6b71a4242de1478
Certificate names · 2 SANs
  • *.netlify.app
  • netlify.app

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

Latest Classified Outcome 2026-10-30 12:10:24 UTC

The site was serving its pages at the latest check.

Technical details
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: Stale Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-30 12:10:24 UTC
RDAP registration
Observed timeline last reachable: 2026-10-30 12:10:24 UTC last content: 2026-10-30 12:10:24 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.
Technologies · 2 identified
Detected via Cloudflare Radar · Wappalyzer engine
Report This Domain Submit evidence & help protect others
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of drop-token.netlify.app · checked Oct 29, 2026

87
Needs Work
Performance
FCP
0.83 s
First Contentful Paint
LCP
2.35 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
437 ms
Total Blocking Time
SI
2.44 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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.

Captured network requests

Network requests: 24 SHA-256 hashes: 19 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 14:08 UTC.

Open this scan on URLScan 01a187f8-253f-724e-9688-61fdee7a8596 ↗

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

    live_content

    content_served

  2. Domain monitor · First collection record

    Reachable

All retained availability observations6

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_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-30 13:10:24.000000
    Evidence SHA-256
    0d9ce043716337e2550da6e11dc88585a18c624fffd9e4ef6939ef87fba911aa
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:24
    Evidence reason
    alive_content
  2. 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-30 13:10:24.000000
    Evidence SHA-256
    0d9ce043716337e2550da6e11dc88585a18c624fffd9e4ef6939ef87fba911aa
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 13:10:24
    Evidence reason
    alive_content
  3. 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-30 01:23:30.000000
    Evidence SHA-256
    8bb9225e2443347c9c7b79fbd7fdb2aef2d656ae6d1913bbd913c9aced35d366
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:30
    Evidence reason
    alive_content
  4. 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-30 01:23:30.000000
    Evidence SHA-256
    8bb9225e2443347c9c7b79fbd7fdb2aef2d656ae6d1913bbd913c9aced35d366
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 01:23:30
    Evidence reason
    alive_content
  5. 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-29 15:03:23.000000
    Evidence SHA-256
    bf45f13b0a9593e94a1a908362fdb40e9dcfcf6a55c3ba7eb30269b72c44a443
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 15:03:23
    Evidence reason
  6. 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-29 15:03:23.000000
    Evidence SHA-256
    bf45f13b0a9593e94a1a908362fdb40e9dcfcf6a55c3ba7eb30269b72c44a443
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 15:03:23
    Evidence reason

Threat Response Pipeline

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

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
    drop-token.netlify.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Blocklist Detection · 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: 99
  • 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.
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • 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 · Monitoring Continues Recorded: 1 of 2
  • DestroyList Published
    Listed in the public repository PhishDestroy/DestroyList
  • Monitoring Continues
    The domain remains reachable or access-restricted; future checks may update this observation.

Recorded activity

3 entries
  1. VirusTotal

    0/92 engine detections

    View source
  2. Added to PhishDestroy

    drop-token.netlify.app

    View source
  3. URLScan

    Page captured

    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.

Lookalike domains

172 stored lookalike domains

xn--optimim-ipb.io homoglyph Internal report A 92.118.112.149NS ns1.dyna-ns.net ethercum.org homoglyph Internal report A 188.114.96.3NS bart.ns.cloudflare.com etheruem.org transposition Internal report A 212.99.218.66NS ns-1511.awsdns-60.org uniswapc.org addition Internal report A 188.114.96.3NS ligia.ns.cloudflare.com uniswapn.org addition Internal report A 188.114.96.3NS ligia.ns.cloudflare.com uniswaq.org bitsquatting Internal report A 31.207.74.154NS bethany.ns.cloudflare.com opltimism.io insertion NS ns1.domaindiscount24.net optimi.sm.io subdomain A 3.139.159.151 optimis.io omission A 51.91.236.193MX alt1.aspmx.l.google.comNS dns104.ovh.net optimise.io bitsquatting A 13.248.169.48NS ns3.afternic.com optimisrn.io homoglyph NS 1-ceci.njalla.do optimizm.io replacement A 104.21.21.200NS grace.ns.cloudflare.com
Show all (88)
optimjsm.io replacement NS 1-ceci.njalla.do optimlsm.io homoglyph NS 1-ceci.njalla.do optimusm.io replacement A 188.114.96.3NS autumn.ns.cloudflare.com optirnism.io homoglyph A 104.21.75.127NS mario.ns.cloudflare.com optirnlsm.io homoglyph A 104.21.77.113NS mario.ns.cloudflare.com optomism.io replacement A 34.42.100.71NS ns-cloud-e1.googledomains.com 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 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 athereum.org bitsquatting A 199.188.200.6MX mail.athereum.orgNS dns1.namecheaphosting.com dethereum.org insertion A 216.198.79.1NS liv.ns.cloudflare.com e.thereum.org subdomain A 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.com efhereum.org replacement A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ehereum.org omission A 15.197.225.128NS ns65.domaincontrol.com etereum.org omission A !ServFailNS !ServFail eth3reum.org replacement A 15.197.142.173NS ns31.domaincontrol.com ether.eum.org subdomain A 13.248.169.48NS ns1.afternic.com etheream.org vowel-swap A 162.255.119.154MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethereim.org replacement A 15.197.142.173NS ns33.domaincontrol.com ethereium.org insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com etherem.org omission A 15.197.225.128NS ns39.domaincontrol.com etheremu.org transposition A 13.248.169.48NS ns1.afternic.com ethereom.org vowel-swap A 192.0.78.24NS ns1.wordpress.com etheresum.org insertion A 104.21.87.66NS aron.ns.cloudflare.com ethereujm.org insertion A 104.21.46.240NS jerry.ns.cloudflare.com ethereum2.org addition A 24.199.74.33NS ns3.namefi.io ethereum3.org addition NS a.share-dns.com ethereum4.org addition A 198.54.117.242NS failed-whois-verification.namecheap.com ethereumc.org addition A 188.114.96.3NS camilo.ns.cloudflare.com ethereumd.org addition A 188.114.96.3NS earl.ns.cloudflare.com ethereumorg.com various NS ns1.openprovider.nl ethereumr.org addition A 188.114.96.3NS monroe.ns.cloudflare.com ethereums.org addition A 15.197.148.33MX mailstore1.secureserver.netNS ns73.domaincontrol.com ethereumx.org addition A 64.190.63.222MX localhostNS ns1.sedoparking.com ethereun.org homoglyph A 52.20.84.62NS ns1.squadhelp.com ethereunm.org homoglyph A 104.21.86.145NS koa.ns.cloudflare.com ethereurm.org homoglyph A 188.114.96.3NS rita.ns.cloudflare.com ethereurn.org homoglyph MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethereuym.org insertion A 104.21.22.142NS everton.ns.cloudflare.com ethereuzm.org insertion A 188.114.96.3NS dale.ns.cloudflare.com ethereyum.org insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com etherium.org vowel-swap A 32.216.8.188NS ns1.no-ip.com etherrum.org replacement MX eforward1.registrar-servers.comNS dns1.registrar-servers.com etherteum.org insertion A 13.248.243.5NS ns41.domaincontrol.com etherum.org omission A 103.224.212.201MX park-mx.above.comNS ns1.abovedomains.com ethezeum.org bitsquatting A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ethireum.org vowel-swap A 192.64.119.29MX eforward1.registrar-servers.comNS dns1.registrar-servers.com ethnereum.org insertion A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ethreum.org omission A 15.197.225.128NS ns65.domaincontrol.com ethureum.org bitsquatting A 162.255.119.109MX eforward1.registrar-servers.comNS dns1.registrar-servers.com etihereum.org homoglyph A 172.233.221.214MX mx156.hostedmxserver.comNS ns1.ns306.parklogic.com ithereum.org vowel-swap A 188.114.96.3NS celine.ns.cloudflare.com othereum.org vowel-swap NS ns-cloud-a1.googledomains.com rethereum.org insertion A 54.36.108.60MX eforward1.registrar-servers.comNS dns1.registrar-servers.com sethereum.org insertion A !ServFailNS !ServFail thereum.org omission A 103.224.212.210MX park-mx.above.comNS ns15.abovedomains.com uthereum.org bitsquatting A 15.197.148.33NS ns15.domaincontrol.com zethereum.org insertion NS ns-1335.awsdns-38.org zthereum.org replacement NS ns-1294.awsdns-33.org aniswap.org vowel-swap NS kanye.ns.cloudflare.com iuniswap.org insertion A 185.66.140.182MX iuniswap.orgNS ns13.knownsrv.com niswap.org omission A !ServFailNS !ServFail nuiswap.org transposition A !ServFailNS !ServFail

Showing 100 of 172

Check for cloaking

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

drop-token.netlify.app

Evidence & External Reports

Deep Analysis
Help & reporting

Were You Affected by This Site?

2 evidence signal groups linked Last known active
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.

Official reporting routes

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.

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 drop-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

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.

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.

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/drop-token.netlify.app"
  title="PhishDestroy threat report for drop-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>