Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 4. 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
memes-claims.netlify.app favicon

memes-claims.netlify.app

In short

memes-claims.netlify.app is a fake airdrop scam detected by PhishDestroy on 2026-10-23. Risk: critical (83/100). Registrar: Netlify. Status: Last known active. Hosting: Amazon.com, Inc. VirusTotal: 4/92 engines flag it. Do not enter credentials or connect a wallet.

“Solana Token — $TOKEN Airdrop”

Review the evidence
Registrar
Netlify
Resolved IP
63.176.8.218
PhishDestroy assessment Critical
83/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 4/92 Stored blocklist matches: 2 Automated brand label: Jito Scam type: Crypto Drainer
VirusTotal
4 / 92
engine detections ·
OTX
0
community references
Page captures
8
open gallery
Oct 23, 2026 CDN
X Telegram API

Questions about memes-claims.netlify.app

Is memes-claims.netlify.app legit?

No. PhishDestroy classifies memes-claims.netlify.app as a fake airdrop scam (risk: critical, 83/100); it was first detected on 2026-10-23. VirusTotal: 4/92 engines flag it. Treat the site as unsafe.

Is memes-claims.netlify.app safe to connect a wallet?

No. Do not connect a wallet, sign messages or approve tokens on memes-claims.netlify.app. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.

What should I do if I used memes-claims.netlify.app?

Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 4 / 92 7 sources

VirusTotal

4 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
1
Suspicious
0
Undetected
37

Vendor labels

Forcepoint ThreatSeeker
phishing

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::258
  • TTL, seconds
    120
    Type
    A
    Value
    98.84.224.111
  • TTL, seconds
    311
    Type
    AAAA
    Value
    2600:1f18:16e:df01::259

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": 54,
    "malicious": 1,
    "suspicious": 0,
    "undetected": 37
}
Vendor labels
{
    "Forcepoint ThreatSeeker": "phishing"
}
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-02T00:13:43Z
DNS records
[
    {
        "ttl": 120,
        "type": "A",
        "value": "18.208.88.157"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::258"
    },
    {
        "ttl": 120,
        "type": "A",
        "value": "98.84.224.111"
    },
    {
        "ttl": 311,
        "type": "AAAA",
        "value": "2600:1f18:16e:df01::259"
    }
]
Dns at
2026-10-23T00:41:15Z
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 · 1 malicious + 0 suspicious / 92 · 2026-10-23 00:35:18 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-23T00:35:18Z
fetched_at
2026-10-23T00:55:12Z
stats
{"timeout":0,"harmless":54,"malicious":1,"suspicious":0,"undetected":37}

URLScan

Malicious · engine verdict · score 100

SHA-256 80f242cbfe157b7421336f12a9741a8c94c09b117a2f882b7a83f7d012403da0

Open report
URLScanOriginal source recordObserved: 22 fields

Observed: · Retrieved:

Report ID

01a16612-4c6d-732a-ba9f-e53214ff4c44

Final URL

https://memes-claims.netlify.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://memes-claims.netlify.app/
    From
    http://memes-claims.netlify.app/
    Status
    307

IP address

63.176.8.218

Reverse DNS (PTR)

ec2-63-176-8-218.eu-central-1.compute.amazonaws.com

Contacted domains

  • www.google.com
  • sprinkler-fondling.data-repo.cc
  • api.dicebear.com
  • t2.gstatic.com
  • t0.gstatic.com
  • t3.gstatic.com
  • fonts.gstatic.com
  • fonts.googleapis.com
  • t1.gstatic.com

Contacted IP addresses

  • 142.251.127.94
  • 185.111.111.156
  • 142.251.13.95
  • 142.251.14.105
  • 192.178.183.147
  • 142.250.154.99
  • 142.251.14.103
  • 142.251.153.119
  • 188.114.96.3
  • 63.176.8.218

Autonomous systems (ASN)

  • 15169
  • 212238
  • 13335
  • 16509

Server countries

  • US
  • DE

Document hash

f72a75794519bab72d11d63a7923309429fef32a6215da24e530fbeb581c76d3

JavaScript globals

  • openModal
  • _uwmc
  • litPropertyMetadata
  • reactiveElementVersions
  • litHtmlVersions
  • litElementVersions

Browser storage keys

  • _0x12
  • _0x5

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

20

Registered domain age, days

20

Certificate age, days

249

Certificate validity, days

396

Page requests

17

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
100
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
01a16612-4c6d-732a-ba9f-e53214ff4c44
Final url
https://memes-claims.netlify.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://memes-claims.netlify.app/",
        "from": "http://memes-claims.netlify.app/",
        "status": 307
    }
]
Ip
63.176.8.218
Ptr
ec2-63-176-8-218.eu-central-1.compute.amazonaws.com
Contacted domains
[
    "www.google.com",
    "sprinkler-fondling.data-repo.cc",
    "api.dicebear.com",
    "t2.gstatic.com",
    "t0.gstatic.com",
    "t3.gstatic.com",
    "fonts.gstatic.com",
    "fonts.googleapis.com",
    "t1.gstatic.com"
]
Contacted IP addresses
[
    "142.251.127.94",
    "185.111.111.156",
    "142.251.13.95",
    "142.251.14.105",
    "192.178.183.147",
    "142.250.154.99",
    "142.251.14.103",
    "142.251.153.119",
    "188.114.96.3",
    "63.176.8.218"
]
Asns
[
    "15169",
    "212238",
    "13335",
    "16509"
]
Countries
[
    "US",
    "DE"
]
Document hash
f72a75794519bab72d11d63a7923309429fef32a6215da24e530fbeb581c76d3
Globals
[
    "openModal",
    "_uwmc",
    "litPropertyMetadata",
    "reactiveElementVersions",
    "litHtmlVersions",
    "litElementVersions"
]
Storage keys
[
    "_0x12",
    "_0x5"
]
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
20
Apex age days
20
Tls age days
249
Tls valid days
396
Requests
17
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 100,
        "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-23 03:30 UTC

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

record_source
domain_monitor.urlscan
uuid
01a16612-4c6d-732a-ba9f-e53214ff4c44
score
0
malicious
false
result_at
2026-10-23T03:30:22Z
enriched_at
2026-10-23T08:16:59Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:22","urlscan_enriched_at":"2026-10-23 10:16:59"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

83 / 100 · heuristic score · 4 brand references · 1 classification

Open report
Separate monitor score · 15 / 100 · 2026-10-23T02:20:28Z

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-23T02:20:28Z
source_timestamp
2026-10-23 04:20:28
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: 21 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

Web archive observations

Last observation
First observation
Recorded changes
0
Archived days
1
Average page size, bytes
9484

Page title and metadata

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

Trackers

Requests
16
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
13
TLS
8
Waiting
867
Connection
8
Download
15
Response time, ms
911

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
40339
CO₂, grams
0.0015
Cleaner than, %
42

DNS servers

Nameservers
  • IP address
    198.51.45.65
    Host
    dns4.p01.nsone.net
  • 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
DNS zone
netlify.app

Location

IP address
2a05:d014:58f:6200::258
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::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://memes-claims.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
}
Web archive observations
{
    "last": "2026-10-02T00:41:46Z",
    "first": "2026-10-02T00:41:46Z",
    "changes": 0,
    "days_archived": 1,
    "avg_page_bytes": 9484
}
Page title and metadata
{
    "ogUrl": "https://memes-claims.netlify.app/",
    "title": "Solana Token — $TOKEN Airdrop",
    "ogType": "website",
    "ogImage": "https://memes-claims.netlify.app/og-base.png",
    "ogTitle": "Solana Token — $TOKEN Airdrop",
    "description": "Solana Token · Claim the $TOKEN airdrop and explore the latest Solana token information.",
    "twitterCard": "summary_large_image",
    "ogDescription": "Solana Token · Claim the $TOKEN airdrop and explore the latest Solana token information."
}
Trackers
{
    "requests": 16,
    "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": 13,
        "tls": 8,
        "wait": 867,
        "connect": 8,
        "download": 15
    },
    "response_ms": 911
}
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": 40339,
    "co2_grams": 0.0015,
    "cleaner_than": 42
}
Dns server
{
    "ns": [
        {
            "ip": "198.51.45.65",
            "host": "dns4.p01.nsone.net"
        },
        {
            "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"
        }
    ],
    "zone": "netlify.app"
}
Location
{
    "ip": "2a05:d014:58f:6200::258",
    "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::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://memes-claims.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 · 8 captures

Primary capture 1 / 8
SourcePrimary capture
Recorded
StateStored capture
Position1 / 8
Open capture Wayback Download
All capture links and hashes (8)
memes-claims.netlify.app: Crypto scam — Blocked by MetaMask, flagged by SEAL, 4/92 VirusTotal engines. PhishDestroy risk score 83/100 (critical).
Social preview card memes-claims.netlify.app: Crypto scam — Blocked by MetaMask, flagged by SEAL, 4/92 VirusTotal engines. PhishDestroy risk score 83/100 (critical). v 8d3033569621

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 100 report ↗
IP Context 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
Technical detailsProvenance & timestamps
First DetectedOct 23, 2026
DOM Analysisanalyzed Oct 23, 2026score 83/1004 brand signals
Submitted URLhttp://memes-claims.netlify.app/
Favicon Hash
Observed page title
Solana Token — $TOKEN Airdrop
Automated brand references
Jito Marinade Orca Solana
TLS Certificate
Issued by DigiCert Global G2 TLS RSA SHA256 2020 CA1 · stored validity ends in 144 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
63.176.8.218
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
AWS EC2 (eu-central-1)
Observed location
Frankfurt, 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.

viewdns.info · 63.176.8.218rapiddns.io

Latest Classified Outcome 2026-10-25 23:01:57 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-25 23:01:57 UTC
RDAP registration
Observed timeline last reachable: 2026-10-25 23:01:57 UTC last content: 2026-10-25 23:01:57 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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

4 / 92 security vendors flagged this domain
View on VT
Last analyzed
alphaMountain.ai
Forcepoint ThreatSeeker
Fortinet
SOCRadar
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    live_content

    content_served

  2. 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_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-26 00:01:57.000000
    Evidence SHA-256
    44d31dce10c87964150e52b9e3bb731f04b900e721b4cce41c40cf20109317fa
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:01:57
    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-26 00:01:57.000000
    Evidence SHA-256
    44d31dce10c87964150e52b9e3bb731f04b900e721b4cce41c40cf20109317fa
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:01:57
    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-25 12:02:09.000000
    Evidence SHA-256
    7edce53a6800d7912fe6b09012b302f6286c73cac3d087f7e36253ec98fe8974
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:02:09
    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-25 12:02:09.000000
    Evidence SHA-256
    7edce53a6800d7912fe6b09012b302f6286c73cac3d087f7e36253ec98fe8974
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:02:09
    Evidence reason
    alive_content
  5. 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-25 03:54:47.000000
    Evidence SHA-256
    c9afe01b22081a4672d726f9cce4ba3eb1111b1833796e54b4143bbdf9fe546a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:47
    Evidence reason
    alive_content
  6. 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-25 03:54:47.000000
    Evidence SHA-256
    c9afe01b22081a4672d726f9cce4ba3eb1111b1833796e54b4143bbdf9fe546a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:47
    Evidence reason
    alive_content
  7. 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-24 12:00:51.000000
    Evidence SHA-256
    81f145cd2868ba5b9a859e432d36c5d176095bc627c172cfbe662235ca2cfcd6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:00:51
    Evidence reason
    alive_content
  8. 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-24 12:00:51.000000
    Evidence SHA-256
    81f145cd2868ba5b9a859e432d36c5d176095bc627c172cfbe662235ca2cfcd6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 12:00:51
    Evidence reason
    alive_content
  9. 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-24 00:00:58.000000
    Evidence SHA-256
    07b6bd8c6251096cc647b057d7092f162ef84d0f334a40baeb6c93cea595dc23
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:00:58
    Evidence reason
    alive_content
  10. 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-24 00:00:58.000000
    Evidence SHA-256
    07b6bd8c6251096cc647b057d7092f162ef84d0f334a40baeb6c93cea595dc23
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:00:58
    Evidence reason
    alive_content
  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-23 12:00:49.000000
    Evidence SHA-256
    956394a74c8cced6ab489d41f2efbe2a3ef8d610d783a83391538b94934dc362
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:00:49
    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-23 12:00:49.000000
    Evidence SHA-256
    956394a74c8cced6ab489d41f2efbe2a3ef8d610d783a83391538b94934dc362
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-23 12:00:49
    Evidence reason
    alive_content
  13. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 02:05:26.000000
    Evidence SHA-256
    efd7e778776b3c4fe352941774fb0a866ec9e8488b87b91b510f5a586ec715fc
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 02:05:26
    Evidence reason
  14. http_observationunknown
    Observation source
    http_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    unknown
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    20
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 02:05:26.000000
    Evidence SHA-256
    efd7e778776b3c4fe352941774fb0a866ec9e8488b87b91b510f5a586ec715fc
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-23 02:05:26
    Evidence reason

Threat Response Pipeline

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

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
    memes-claims.netlify.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · VirusTotal · Blocklist Detection · Brand Impersonation · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 7 of 7
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 100
  • VirusTotal
    Detections recorded on VirusTotal: 4/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Brand Impersonation
    Automated brand label: Jito
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, URLQuery, 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

    4/92 engine detections

    View source
  2. Added to PhishDestroy

    memes-claims.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.

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

Check for cloaking

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

memes-claims.netlify.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 4 det. ChainPatrol URLQuery Report stored SSL Labs Stored certificate dates valid WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis
Help & reporting

Were You Affected by This Site?

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

If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.

Immediate steps Find reporting contacts

Official reporting routes

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

Even if funds were frozen, they cannot be recovered without an official police report or court order. Submitting a complaint is the only path to potential recovery.

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.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including memes-claims.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/memes-claims.netlify.app"
  title="PhishDestroy threat report for memes-claims.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>