Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 2. 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
sol-incinerator-o3hbp6sam-solslugs.vercel.app favicon

sol-incinerator-o3hbp6sam-solslugs.vercel.app

In short

PhishDestroy stores a record for sol-incinerator-o3hbp6sam-solslugs.vercel.app. Source observations are dated separately; missing checks do not establish safety.

“Reclaim SOL from Empty Token Accounts | Sol Incinerator”

Review the evidence
Registrar
United StatesVercel
Resolved IP
United States64.29.17.3Amazon.com, Inc. · CDN
First observed
Oct 22, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 2/92 Stored blocklist matches: 2
VirusTotal
2 / 92
engine detections ·
Blocklist matches
2
MetaMask, SEAL
URLScan
Malicious
engine verdict · score 99
Page captures
4
open gallery
Oct 22, 2026 CDN
X Telegram API

Questions about sol-incinerator-o3hbp6sam-solslugs.vercel.app

Is sol-incinerator-o3hbp6sam-solslugs.vercel.app legit?

PhishDestroy stores a record for sol-incinerator-o3hbp6sam-solslugs.vercel.app. Source observations are dated separately; missing checks do not establish safety.

Is sol-incinerator-o3hbp6sam-solslugs.vercel.app safe to connect a wallet?

This report does not record which wallet requests sol-incinerator-o3hbp6sam-solslugs.vercel.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 sol-incinerator-o3hbp6sam-solslugs.vercel.app?

It depends on what you did. If you entered a password, change it, and also on every other site where you used the same password; turn on two-factor authentication where it is offered. If you paid or gave card or bank details, contact your bank or payment service through the contacts on your card or its official website. If you only connected a wallet, disconnect the site in the wallet and reject pending requests; a connection by itself does not move funds. If you signed a token approval or permit, revoke it with a token-approval checker. If you shared a seed phrase or private key, treat the wallet as compromised and move the remaining funds to a new wallet with a new seed phrase. If you downloaded a file, do not open it and scan the device with security software. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority; a report does not guarantee that money is returned. Step-by-step help: emergency guide.

Explore

Source evidenceVirusTotal 2 / 92 7 sources

VirusTotal

2 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 15 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
54
Malicious
2
Suspicious
0
Undetected
36

Vendor labels

ChainPatrol
malicious
alphaMountain.ai
malicious

Reputation score

0

Tags

  • dga

Categories

alphaMountain.ai
Information Technology, Malicious (alphaMountain.ai)

Registrar

Tucows Domains Inc

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    300
    Type
    A
    Value
    64.29.17.3
  • TTL, seconds
    300
    Type
    A
    Value
    216.198.79.3

DNS records observed

JARM fingerprint

3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb

Certificate

Subject alternative names
  • *.vercel.app
Issuer
Google Trust Services / WR1
Serial
f7911168ffa7d0f4135e24792e7a52a8
SHA-256
8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Subject
*.vercel.app
Valid until
Valid from

Registration record

Registrar
Tucows Domains Inc
Registrar IANA ID
69
Registrar URL
http://www.tucows.com
Registered
Updated
Expires
Status
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.vercel-dns-3.com
  • ns2.vercel-dns-3.com
  • ns3.vercel-dns-3.com
  • ns4.vercel-dns-3.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 54,
    "malicious": 2,
    "suspicious": 0,
    "undetected": 36
}
Vendor labels
{
    "ChainPatrol": "malicious",
    "alphaMountain.ai": "malicious"
}
Reputation
0
Tags
[
    "dga"
]
Categories
{
    "alphaMountain.ai": "Information Technology, Malicious (alphaMountain.ai)"
}
Registrar
Tucows Domains Inc
Created
2020-01-28T03:03:04Z
Expires
2026-01-28T03:03:04Z
Updated
2025-01-26T03:25:55Z
First seen
2026-10-18T11:11:49Z
DNS records
[
    {
        "ttl": 300,
        "type": "A",
        "value": "64.29.17.3"
    },
    {
        "ttl": 300,
        "type": "A",
        "value": "216.198.79.3"
    }
]
Dns at
2026-10-18T11:11:51Z
Jarm
3fd3fd00000000000043d43d00043dc3b2afa8a5ec09b510a8559aff7899fb
Certificate
{
    "san": [
        "*.vercel.app"
    ],
    "issuer": "Google Trust Services / WR1",
    "serial": "f7911168ffa7d0f4135e24792e7a52a8",
    "sha256": "8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093",
    "subject": "*.vercel.app",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Registration record
{
    "registrar": "Tucows Domains Inc",
    "registrar_iana_id": "69",
    "registrar_url": "http://www.tucows.com",
    "created": "2020-01-28T03:03:04Z",
    "updated": "2025-01-26T03:25:55Z",
    "expires": "2026-01-28T03:03:04Z",
    "status": [
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.vercel-dns-3.com",
        "ns2.vercel-dns-3.com",
        "ns3.vercel-dns-3.com",
        "ns4.vercel-dns-3.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 2 malicious + 0 suspicious / 92 · 2026-10-18 11:04:02 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-18T11:04:02Z
fetched_at
2026-10-22T22:03:35Z
stats
{"timeout":0,"harmless":54,"malicious":2,"suspicious":0,"undetected":36}

URLScan

Malicious · engine verdict · score 99

SHA-256 6e642719513780a7df9352e6371ec1eb35f45b2c29c9f608371183140aee8665

Open report
URLScanOriginal source recordObserved: 25 fields

Observed: · Retrieved:

Report ID

01a16586-c49a-7308-8129-8c58f8dc52d1

Final URL

https://sol-incinerator-o3hbp6sam-solslugs.vercel.app/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://sol-incinerator-o3hbp6sam-solslugs.vercel.app/
    From
    http://sol-incinerator-o3hbp6sam-solslugs.vercel.app/
    Status
    307

IP address

64.29.17.67

Contacted domains

  • www.google.com
  • api.web3modal.org
  • www.google.ca
  • ad.doubleclick.net
  • googleads.g.doubleclick.net
  • www.googletagmanager.com

Contacted IP addresses

  • 104.18.19.237
  • 142.250.31.94
  • 192.178.155.148
  • 142.251.156.119
  • 172.253.115.156
  • 64.233.180.97
  • 64.29.17.67

Autonomous systems (ASN)

  • 13335
  • 15169
  • 16509

Server countries

  • US

Linked domains

  • docs.sol-incinerator.com
  • x.com

Social media links

  • https://x.com/solincinerator

Document hash

80ef4ed8b78cfe709ba8b770690888152e1a7a6f644d8511e7d4eecb8e9f3fc1

Script hashes

  • 6071bc1beddfb3b99ad15208aa7f4a313f332e15ba6f647ece920bdac0f617fc
  • ac61824cbe55db2ff6a8d8a22e8427dc3ddba120242a077e944ee4159ed7c5fc
  • dc51f1594ed2484aa062ec37d73405d72f869301be17831ff9abd33863bed69e
  • b018a89725f181af8c271946d6a8544cffa6cd05f3344671058a9e22f523f1da
  • 42dae3902b97554c6004d5c0f87c83813471a05b6e85768dfe38c803a6b4ef0e
  • d0229b8518bb3bece81ba28c1e5e3791456d88a81b3df0b860a715932a6af0a7
  • 179cd6cff6e4654a0b0cf549e3a2dd7d8469d4bbd4ea6627a3b3230e8f32a310
  • 77be01b8fa437ad876ac7344ba7af02a738d0a92e7c471b1352f1de1db8ca2f0
  • 68253c13dd2db173ad2aaab07b7a5325d2b4f92339d0696708c11d9b72117049
  • 4e68fbb17126e00ed1dd699eaa2793400fdd422358c1304375802e35790e2256

JavaScript globals

  • __next_s
  • __siPerformanceState
  • __siEarlyConnect
  • $RB
  • $RV
  • $RC
  • __next_f
  • $RT
  • webpackChunk_N_E
  • next
  • _N_E_STYLE_LOAD
  • gtag
  • dataLayer
  • google_tag_data
  • google_tag_manager
  • GooglebQhCsO
  • litPropertyMetadata
  • reactiveElementVersions
  • litHtmlVersions
  • litElementVersions
  • clearMWACache
  • _walletConnectCore__count
  • _walletConnectCore_

Cookies

  • _gcl_au
  • test_cookie

Browser storage keys

  • si:product-analytics:session:v1
  • _gcl_ls
  • @appkit/active_caip_network_id
  • @appkit/active_namespace
  • @appkit/connection_status
  • @appkit/disconnected_connector_ids

TLS session and certificate

Subject alternative names
  • *.vercel.app
Cipher
AES_128_GCM
Issuer
WR1
Subject
*.vercel.app
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

4

Registered domain age, days

4

Certificate age, days

54

Certificate validity, days

89

Page requests

80

Provider verdicts

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

HTTP headers

Server
Vercel
Content-type
text/html; charset=utf-8
X-powered-by
Next.js
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Uuid
01a16586-c49a-7308-8129-8c58f8dc52d1
Final url
https://sol-incinerator-o3hbp6sam-solslugs.vercel.app/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://sol-incinerator-o3hbp6sam-solslugs.vercel.app/",
        "from": "http://sol-incinerator-o3hbp6sam-solslugs.vercel.app/",
        "status": 307
    }
]
Ip
64.29.17.67
Contacted domains
[
    "www.google.com",
    "api.web3modal.org",
    "www.google.ca",
    "ad.doubleclick.net",
    "googleads.g.doubleclick.net",
    "www.googletagmanager.com"
]
Contacted IP addresses
[
    "104.18.19.237",
    "142.250.31.94",
    "192.178.155.148",
    "142.251.156.119",
    "172.253.115.156",
    "64.233.180.97",
    "64.29.17.67"
]
Asns
[
    "13335",
    "15169",
    "16509"
]
Countries
[
    "US"
]
Linked domains
[
    "docs.sol-incinerator.com",
    "x.com"
]
Social
[
    "https://x.com/solincinerator"
]
Document hash
80ef4ed8b78cfe709ba8b770690888152e1a7a6f644d8511e7d4eecb8e9f3fc1
Script hashes
[
    "6071bc1beddfb3b99ad15208aa7f4a313f332e15ba6f647ece920bdac0f617fc",
    "ac61824cbe55db2ff6a8d8a22e8427dc3ddba120242a077e944ee4159ed7c5fc",
    "dc51f1594ed2484aa062ec37d73405d72f869301be17831ff9abd33863bed69e",
    "b018a89725f181af8c271946d6a8544cffa6cd05f3344671058a9e22f523f1da",
    "42dae3902b97554c6004d5c0f87c83813471a05b6e85768dfe38c803a6b4ef0e",
    "d0229b8518bb3bece81ba28c1e5e3791456d88a81b3df0b860a715932a6af0a7",
    "179cd6cff6e4654a0b0cf549e3a2dd7d8469d4bbd4ea6627a3b3230e8f32a310",
    "77be01b8fa437ad876ac7344ba7af02a738d0a92e7c471b1352f1de1db8ca2f0",
    "68253c13dd2db173ad2aaab07b7a5325d2b4f92339d0696708c11d9b72117049",
    "4e68fbb17126e00ed1dd699eaa2793400fdd422358c1304375802e35790e2256"
]
Globals
[
    "__next_s",
    "__siPerformanceState",
    "__siEarlyConnect",
    "$RB",
    "$RV",
    "$RC",
    "__next_f",
    "$RT",
    "webpackChunk_N_E",
    "next",
    "_N_E_STYLE_LOAD",
    "gtag",
    "dataLayer",
    "google_tag_data",
    "google_tag_manager",
    "GooglebQhCsO",
    "litPropertyMetadata",
    "reactiveElementVersions",
    "litHtmlVersions",
    "litElementVersions",
    "clearMWACache",
    "_walletConnectCore__count",
    "_walletConnectCore_"
]
Cookies
[
    "_gcl_au",
    "test_cookie"
]
Storage keys
[
    "si:product-analytics:session:v1",
    "_gcl_ls",
    "@appkit/active_caip_network_id",
    "@appkit/active_namespace",
    "@appkit/connection_status",
    "@appkit/disconnected_connector_ids"
]
Tls
{
    "san": [
        "*.vercel.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR1",
    "subject": "*.vercel.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-11-27T19:48:08Z",
    "valid_from": "2026-08-29T19:48:09Z"
}
Domain age days
4
Apex age days
4
Tls age days
54
Tls valid days
89
Requests
80
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 99,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "Vercel",
    "content-type": "text/html; charset=utf-8",
    "x-powered-by": "Next.js",
    "strict-transport-security": "max-age=63072000; 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
01a16586-c49a-7308-8129-8c58f8dc52d1
score
0
malicious
false
result_at
2026-10-23T03:30:35Z
enriched_at
2026-10-23T08:19:25Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:35","urlscan_enriched_at":"2026-10-23 10:19:25"}
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

100 / 100 · heuristic score · 6 brand references · 1 classification

Open report
Separate monitor score · 100 / 100 · 2026-10-22T22:20:34Z

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
100
analyzed_at
2026-10-22T22:20:34Z
source_timestamp
2026-10-23 00:20:34
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: 27 fields

Mail configuration

SPF lookups
0

CAA records

Count
2
Domain
vercel.app
Allowed issuers
  • letsencrypt.org
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

Crawler rules

Present
Yes
llms.txt file
Yes
Sitemap URLs
  • https://sol-incinerator.com/sitemap.xml

Sitemap

Present
Yes
URL count
2180

Security contact file (security.txt)

Present
Yes
Found at
/.well-known/security.txt

Page title and metadata

Open Graph URL
https://sol-incinerator.com
Author
Sol Slugs Team
Open Graph type
website
Indexing directives
index, follow
Open Graph image
https://sol-incinerator.com/og/home.png
Open Graph title
Reclaim SOL from Empty Token Accounts | Sol Incinerator
Keywords
reclaim SOL,claim SOL,recover locked SOL,SOL rent recovery,empty SPL token accounts,Token-2022,close token accounts,Solana wallet cleaner,burn NFT,burn Solana tokens
Open Graph site name
Sol Incinerator
Theme color
#1D2617
Description
Reclaim SOL from empty SPL and Token-2022 accounts with a non-custodial Solana wallet cleaner that also burns unwanted tokens and NFTs.
Twitter card
summary_large_image
Twitter account
@solincinerator
Canonical URL
https://sol-incinerator.com
Open Graph description
Reclaim SOL from empty SPL and Token-2022 accounts with a non-custodial Solana wallet cleaner that also burns unwanted tokens and NFTs.
Twitter Creator
@SolSlugsNFT

Trackers

Requests
32
Observed services
  • Name
    Google
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    3
  • Name
    Google Dynamic Remarketing
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1
  • Name
    Google Marketing Platform
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    2
  • Name
    Google Tag
    Company
    Google
    Country
    US
    Category
    Advertising
    Requests
    1

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
61
TLS
23
Waiting
2592
Connection
8
Download
235
Response time, ms
2919

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
206579
CO₂, grams
0.0076
Cleaner than, %
6

DNS servers

Nameservers
  • IP address
    205.251.193.92
    Host
    ns1.vercel-dns-3.com
  • IP address
    205.251.194.149
    Host
    ns2.vercel-dns-3.com
  • IP address
    205.251.199.60
    Host
    ns4.vercel-dns-3.com
  • IP address
    205.251.197.116
    Host
    ns3.vercel-dns-3.com
DNS zone
vercel.app

Cookies

Cookies
  • Name
    _gcl_au
  • Name
    test_cookie
    Secure
    Yes
    SameSite
    None

Location

IP address
216.198.79.3
ASN
16509
Organization
Amazon.com, Inc.
Country
US

TLS certificate

Issuer
Google Trust Services / WR1
Subject
*.vercel.app

DNS records

A
  • 216.198.79.3
  • 64.29.17.3

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Header value
max-age=63072000; 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=63072000; includeSubDomains; preload
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
216.198.79.3
IP version
4

Redirects

Redirect chain
  • https://sol-incinerator-o3hbp6sam-solslugs.vercel.app

Technology stack

Technologies
  • Node.js
  • React
  • Vercel
  • Next.js
  • Google Ads
  • Google Analytics
  • Google Ads Conversion Tracking
  • lit-html
  • lit-element
  • Priority Hints
  • HSTS
  • Webpack
  • PWA
  • Open Graph
  • Module Federation

Social profiles

Profiles
  • https://x.com/solincinerator

Page links

External link addresses
  • https://docs.sol-incinerator.com/
  • https://x.com/solincinerator
  • https://docs.sol-incinerator.com/terms-of-use
  • https://docs.sol-incinerator.com/privacy-policy
  • https://docs.sol-incinerator.com/security-policy
External links
5
Internal links
6

HTTP headers

Response headers
Server
Vercel
Content-type
text/html; charset=utf-8
X-powered-by
Next.js
Strict-transport-security
max-age=63072000; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 2,
    "domain": "vercel.app",
    "issuers": [
        "letsencrypt.org",
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
Crawler rules
{
    "present": true,
    "llms_txt": true,
    "sitemaps": [
        "https://sol-incinerator.com/sitemap.xml"
    ]
}
Sitemap
{
    "present": true,
    "url_count": 2180
}
Security contact file
{
    "present": true,
    "found_in": "/.well-known/security.txt"
}
Page title and metadata
{
    "ogUrl": "https://sol-incinerator.com",
    "author": "Sol Slugs Team",
    "ogType": "website",
    "robots": "index, follow",
    "ogImage": "https://sol-incinerator.com/og/home.png",
    "ogTitle": "Reclaim SOL from Empty Token Accounts | Sol Incinerator",
    "keywords": "reclaim SOL,claim SOL,recover locked SOL,SOL rent recovery,empty SPL token accounts,Token-2022,close token accounts,Solana wallet cleaner,burn NFT,burn Solana tokens",
    "ogSiteName": "Sol Incinerator",
    "themeColor": "#1D2617",
    "description": "Reclaim SOL from empty SPL and Token-2022 accounts with a non-custodial Solana wallet cleaner that also burns unwanted tokens and NFTs.",
    "twitterCard": "summary_large_image",
    "twitterSite": "@solincinerator",
    "canonicalUrl": "https://sol-incinerator.com",
    "ogDescription": "Reclaim SOL from empty SPL and Token-2022 accounts with a non-custodial Solana wallet cleaner that also burns unwanted tokens and NFTs.",
    "twitterCreator": "@SolSlugsNFT"
}
Trackers
{
    "requests": 32,
    "trackers": [
        {
            "name": "Google",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 3
        },
        {
            "name": "Google Dynamic Remarketing",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        },
        {
            "name": "Google Marketing Platform",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 2
        },
        {
            "name": "Google Tag",
            "company": "Google",
            "country": "US",
            "category": "Advertising",
            "requests": 1
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 61,
        "tls": 23,
        "wait": 2592,
        "connect": 8,
        "download": 235
    },
    "response_ms": 2919
}
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": 206579,
    "co2_grams": 0.0076,
    "cleaner_than": 6
}
Dns server
{
    "ns": [
        {
            "ip": "205.251.193.92",
            "host": "ns1.vercel-dns-3.com"
        },
        {
            "ip": "205.251.194.149",
            "host": "ns2.vercel-dns-3.com"
        },
        {
            "ip": "205.251.199.60",
            "host": "ns4.vercel-dns-3.com"
        },
        {
            "ip": "205.251.197.116",
            "host": "ns3.vercel-dns-3.com"
        }
    ],
    "zone": "vercel.app"
}
Cookies
{
    "cookies": [
        {
            "name": "_gcl_au"
        },
        {
            "name": "test_cookie",
            "secure": true,
            "same_site": "None"
        }
    ]
}
Location
{
    "ip": "216.198.79.3",
    "asn": "16509",
    "org": "Amazon.com, Inc.",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR1",
    "subject": "*.vercel.app"
}
DNS records
{
    "A": [
        "216.198.79.3",
        "64.29.17.3"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=63072000; 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=63072000; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "216.198.79.3",
    "family": 4
}
Redirects
{
    "chain": [
        "https://sol-incinerator-o3hbp6sam-solslugs.vercel.app"
    ]
}
Tech stack
{
    "technologies": [
        "Node.js",
        "React",
        "Vercel",
        "Next.js",
        "Google Ads",
        "Google Analytics",
        "Google Ads Conversion Tracking",
        "lit-html",
        "lit-element",
        "Priority Hints",
        "HSTS",
        "Webpack",
        "PWA",
        "Open Graph",
        "Module Federation"
    ]
}
Social profiles
{
    "profiles": [
        "https://x.com/solincinerator"
    ]
}
Page links
{
    "external": [
        "https://docs.sol-incinerator.com/",
        "https://x.com/solincinerator",
        "https://docs.sol-incinerator.com/terms-of-use",
        "https://docs.sol-incinerator.com/privacy-policy",
        "https://docs.sol-incinerator.com/security-policy"
    ],
    "external_count": 5,
    "internal_count": 6
}
HTTP headers
{
    "headers": {
        "server": "Vercel",
        "content-type": "text/html; charset=utf-8",
        "x-powered-by": "Next.js",
        "strict-transport-security": "max-age=63072000; includeSubDomains; preload"
    }
}
Security Signals
SA Scamadviser Warnings 1/100
The Tranco rank (how much traffic) is rather low An iframe has been detected within the website A (free) development platform is used by this website The server of the site has several low reviewed other websites
We found a valid SSL certificate DNSFilter labels this site as safe
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 · 4 captures

Primary capture 1 / 4
SourcePrimary capture
Recorded
StateStored capture
Position1 / 4
Open capture Wayback Download
All capture links and hashes (4)
sol-incinerator-o3hbp6sam-solslugs.vercel.app: Crypto scam — Blocked by MetaMask, flagged by SEAL, 4/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card sol-incinerator-o3hbp6sam-solslugs.vercel.app: Crypto scam — Blocked by MetaMask, flagged by SEAL, 4/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v 88a53821a3a3

Domain details

Domain
URLScan verdict Analysis completed score 0 Engine verdict: malicious · score 99 report ↗
IP Context United States64.29.17.3 Vercel shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Vercel US(US)
Abuse contactabuse@vercel.com
Hosting abuse contact abuse@vercel.com Amazon.com, Inc. · AS16509
HTTP Status200
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 23, 2026score 100/1006 brand signals
Submitted URLhttp://sol-incinerator-o3hbp6sam-solslugs.vercel.app/
Favicon Hash
Observed page title
Reclaim SOL from Empty Token Accounts | Sol Incinerator
Automated brand references
Backpack Jupiter Ledger Phantom Solana Solflare
TLS Certificate
Issued by WR1 · stored validity ends in 26 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States64.29.17.3
Network ASN
AS16509
AS name
AMAZON-02 - Amazon.com, Inc., US
Organization
Amazon.com, Inc.
Observed location
United StatesWalnut, US
Server header
Vercel

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WR1
Valid from
2026-08-29 19:48:09
Valid until
2026-11-27 19:48:08
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint8f46c4a0a289bfde4060d06986f2af761ee62d668dde972e6bef4687ee4f6093
Certificate names · 1 SAN
  • *.vercel.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 · 64.29.17.3rapiddns.io

Latest Classified Outcome 2026-10-31 23:13:13 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-31 23:13:13 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:13:13 UTC last content: 2026-10-31 23:13:13 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.
Threat Intel Cross-Reference · source references
ScamAdviser Public lookup
A public ScamAdviser lookup is available. Review its current score and warnings at the source; the existence of a lookup page is not itself a malicious verdict.
View on ScamAdviser
Fetched directly from the site by PhishDestroy · cached up to 24 h
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

2 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 4 detections
ChainPatrol
alphaMountain.ai
Forcepoint ThreatSeeker
SOCRadar

Archived Evidence

Wayback Machine Snapshot
View Archive
Stored Capture Evidence 1 snapshot

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

Archived HTTP response HTTP 200
Requested URL: http://sol-incinerator-o3hbp6sam-solslugs.vercel.app/
Final URL: https://sol-incinerator-o3hbp6sam-solslugs.vercel.app/
Reclaim SOL from Empty Token Accounts | Sol Incinerator
Reclaim SOL from empty SPL and Token-2022 accounts with a non-custodial Solana wallet cleaner that also burns unwanted tokens and NFTs.
Response
HTTP 200
HTML body
201.7 KB
Compressed
43.1 KB
Links
13 internal · 7 external
Detected technologies
react
Selected response headers
Cache-Control: private, no-cache, no-store, max-age=0, must-revalidate
Content-Encoding: gzip
Content-Type: text/html; charset=utf-8
Server: Vercel
X-Powered-By: Next.js
Security headers present
Strict-Transport-Security
HSTS: observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Open Graph title: Reclaim SOL from Empty Token Accounts | Sol Incinerator
Open Graph description: Reclaim SOL from empty SPL and Token-2022 accounts with a non-custodial Solana wallet cleaner that also burns unwanted tokens and NFTs.
Twitter card: summary_large_image
Saved response-header values · 16
Age
0
Cache-Control
private, no-cache, no-store, max-age=0, must-revalidate
Content-Encoding
gzip
Content-Language
en
Content-Type
text/html; charset=utf-8
Date
Mon, 19 Oct 2026 01:22:19 GMT
Link
; rel="alternate"; type="text/markdown", ; rel="describedby"
Server
Vercel
Strict-Transport-Security
max-age=63072000; includeSubDomains; preload
Transfer-Encoding
chunked
Vary
rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch
X-Matched-Path
/
X-Powered-By
Next.js
X-Robots-Tag
noindex
X-Vercel-Cache
MISS
X-Vercel-Id
fra1::iad1::gmlcg-1792372938973-f766f3af0e59

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

Archived
Registration & observation details3

Availability observations

Last reachable observation
Last content observation
Estimate basis
Currently reachable

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

Captured network requests

Network requests: 80 SHA-256 hashes: 75 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 02:01 UTC.

Open this scan on URLScan 01a16586-c49a-7308-8129-8c58f8dc52d1 ↗

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 observations36

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-11-01 00:13:13.000000
    Evidence SHA-256
    dc5605a9be0b87b3ce450b0b4c0e080b3de831fcb3a85569160c2cc8399c490c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:13:13
    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-11-01 00:13:13.000000
    Evidence SHA-256
    dc5605a9be0b87b3ce450b0b4c0e080b3de831fcb3a85569160c2cc8399c490c
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-11-01 00:13:13
    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-31 12:13:50.000000
    Evidence SHA-256
    abc2312a776ee2031d5f8c26b33bbceb997e19261106ec8c63de16a23712bc5d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:13:50
    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-31 12:13:50.000000
    Evidence SHA-256
    abc2312a776ee2031d5f8c26b33bbceb997e19261106ec8c63de16a23712bc5d
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:13:50
    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-31 03:34:51.000000
    Evidence SHA-256
    58974ab3ff9189c58aaed4c2bde21051c07e0ae02474aabe1e62f595fb327858
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:34:51
    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-31 03:34:51.000000
    Evidence SHA-256
    58974ab3ff9189c58aaed4c2bde21051c07e0ae02474aabe1e62f595fb327858
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 03:34:51
    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-30 12:11:32.000000
    Evidence SHA-256
    0b04e6dad7978f0a9a39a4458cf2962be210282928dd3de0658b5821f7e73db9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:11:32
    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-30 12:11:32.000000
    Evidence SHA-256
    0b04e6dad7978f0a9a39a4458cf2962be210282928dd3de0658b5821f7e73db9
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 12:11:32
    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-30 00:11:31.000000
    Evidence SHA-256
    0231eab304e76600fd8947fada9d72d3309cd5a9dbf6b9e75eb06d463df50834
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:11:31
    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-30 00:11:31.000000
    Evidence SHA-256
    0231eab304e76600fd8947fada9d72d3309cd5a9dbf6b9e75eb06d463df50834
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-30 00:11:31
    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-29 12:12:00.000000
    Evidence SHA-256
    f710a8f1594df9a9caa7cb181f2c72bf28ec01ebb0f31771ecabe7af858787af
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:12:00
    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-29 12:12:00.000000
    Evidence SHA-256
    f710a8f1594df9a9caa7cb181f2c72bf28ec01ebb0f31771ecabe7af858787af
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 12:12:00
    Evidence reason
    alive_content
  13. 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-29 03:40:33.000000
    Evidence SHA-256
    081f91a4cee312532b02d6b39b41830b1f5df00a1afc5b5a82314380595acc30
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:40:33
    Evidence reason
    alive_content
  14. 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-29 03:40:33.000000
    Evidence SHA-256
    081f91a4cee312532b02d6b39b41830b1f5df00a1afc5b5a82314380595acc30
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-29 03:40:33
    Evidence reason
    alive_content
  15. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:55.000000
    Evidence SHA-256
    dd29fc538a5f11dffdc612ff1a9b6a634654280fdc66ae57570c1f0670778b83
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:06:55
    Evidence reason
    alive_content
  16. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:55.000000
    Evidence SHA-256
    dd29fc538a5f11dffdc612ff1a9b6a634654280fdc66ae57570c1f0670778b83
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 12:06:55
    Evidence reason
    alive_content
  17. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    stale
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:07:21.000000
    Evidence SHA-256
    9553c064bff940ed45db01f27e007cc954a30c2195656bd310b7e0c9766b0d5a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:07:21
    Evidence reason
    alive_content
  18. http_observationlive_content
    Observation source
    http_observation
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    unknown
    Recorded HTTP status
    200
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    90
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:07:21.000000
    Evidence SHA-256
    9553c064bff940ed45db01f27e007cc954a30c2195656bd310b7e0c9766b0d5a
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-28 00:07:21
    Evidence reason
    alive_content
  19. 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-27 12:06:58.000000
    Evidence SHA-256
    4c0e9f17fc291367661ae6273a5fd8616f18c9659bb536343aefc99a934741e6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:06:58
    Evidence reason
    alive_content
  20. 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-27 12:06:58.000000
    Evidence SHA-256
    4c0e9f17fc291367661ae6273a5fd8616f18c9659bb536343aefc99a934741e6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-27 12:06:58
    Evidence reason
    alive_content
  21. 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 12:01:54.000000
    Evidence SHA-256
    52b0c8aa58c5ee7cf7208391085d80e6629428bd9b8ac483bdbba1e159c1c105
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:01:54
    Evidence reason
    alive_content
  22. 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 12:01:54.000000
    Evidence SHA-256
    52b0c8aa58c5ee7cf7208391085d80e6629428bd9b8ac483bdbba1e159c1c105
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 12:01:54
    Evidence reason
    alive_content
  23. 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:02:07.000000
    Evidence SHA-256
    30163c64513dc0f6c009519f793e9f1dbf39dbc950ed35b61ae0578136a68cf0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:02:07
    Evidence reason
    alive_content
  24. 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:02:07.000000
    Evidence SHA-256
    30163c64513dc0f6c009519f793e9f1dbf39dbc950ed35b61ae0578136a68cf0
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-26 00:02:07
    Evidence reason
    alive_content
  25. 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:13.000000
    Evidence SHA-256
    938df6e137f867015a0fab3b4139bcb0c6588120bb452108638e8eb340c3291e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:02:13
    Evidence reason
    alive_content
  26. 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:13.000000
    Evidence SHA-256
    938df6e137f867015a0fab3b4139bcb0c6588120bb452108638e8eb340c3291e
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 12:02:13
    Evidence reason
    alive_content
  27. 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:49.000000
    Evidence SHA-256
    b05a398c27456a5a0caaf1dd69604f25b38451e2f108bfe60e1a3f6ad0258033
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:49
    Evidence reason
    alive_content
  28. 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:49.000000
    Evidence SHA-256
    b05a398c27456a5a0caaf1dd69604f25b38451e2f108bfe60e1a3f6ad0258033
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-25 03:54:49
    Evidence reason
    alive_content
  29. 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
  30. 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
  31. 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:59.000000
    Evidence SHA-256
    b79def83f8769c86876735cd406fcb9c5dcfd120cf660c4ac75f5abc0aa59b99
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:00:59
    Evidence reason
    alive_content
  32. 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:59.000000
    Evidence SHA-256
    b79def83f8769c86876735cd406fcb9c5dcfd120cf660c4ac75f5abc0aa59b99
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-24 00:00:59
    Evidence reason
    alive_content
  33. 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
  34. 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
  35. 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-22 23:32:50.000000
    Evidence SHA-256
    1ba7e2a5bd557fe4e6caa48bd4e15a2a613eb3f9397c557ad315c8287743543c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 23:32:50
    Evidence reason
  36. 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-22 23:32:50.000000
    Evidence SHA-256
    1ba7e2a5bd557fe4e6caa48bd4e15a2a613eb3f9397c557ad315c8287743543c
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 23:32:50
    Evidence reason

Threat Response Pipeline

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

Recorded events: 10. 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
    sol-incinerator-o3hbp6sam-solslugs.vercel.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Web Archive · VirusTotal · Blocklist Detection · Automated brand label: Ledger · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 8 of 8
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 99
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 2/92
  • Blocklist Detection
    Found in blocklists: MetaMask, SEAL
  • Automated brand label: Ledger
    Collector label, not confirmed by a page check.
  • Forensic Evidence Collected
    Stored evidence from URLScan.io, stored screenshot
  • Technical Analysis Recorded
    The report contains stored results of technology detection or forensic analysis.
Publication & AvailabilityDestroyList Published · 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

4 entries
  1. Added to PhishDestroy

    sol-incinerator-o3hbp6sam-solslugs.vercel.app

    View source
  2. URLScan

    Page captured

    View source
  3. Wayback Machine

    Page archived

    View source
  4. VirusTotal

    2/92 engine detections

    View source
How we investigate & report

Public scans, evidence and abuse channels

We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.

01Public scans & evidence collection10 sources and tool groups
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

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

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

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

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.

Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Lookalike domains

151 stored lookalike domains

ledfger.com insertion Internal report A 185.244.151.84MX ledfger.comNS ns3.ro.hostsailor.com ledgfer.com insertion Internal report A 185.244.151.84MX ledgfer.comNS ns3.ro.hostsailor.com ledgher.com insertion Internal report A 185.244.151.84MX ledgher.comNS ns3.ro.hostsailor.com ledgrr.com replacement Internal report A 185.244.151.84MX ledgrr.comNS ns3.ro.hostsailor.com lefdger.com insertion Internal report A 185.244.151.84MX lefdger.comNS ns3.ro.hostsailor.com lesdger.com insertion Internal report A 185.244.151.84MX lesdger.comNS ns3.ro.hostsailor.com lkedger.com insertion Internal report A 185.244.151.84MX lkedger.comNS ns3.ro.hostsailor.com lredger.com insertion Internal report A 185.244.151.84MX lredger.comNS ns3.ro.hostsailor.com lwedger.com insertion Internal report A 185.244.151.84MX lwedger.comNS ns3.ro.hostsailor.com xn--ledgr-9za.com homoglyph Internal report NS ns-cloud-d1.googledomains.com ledgerk.com addition Internal report A 156.250.67.229NS ns1.bdydns.cn edger.com omission A 54.215.31.113NS ns1.dyna-ns.net
Show all (88)
eldger.com transposition A 185.244.151.84MX eldger.comNS ns3.ro.hostsailor.com kedger.com replacement A 13.56.33.8NS ns1.brandbucket.com kledger.com insertion A 20.65.18.151NS ns-1490.awsdns-58.org l3dger.com replacement A 216.198.79.1MX inbound-smtp.eu-west-1.amazonaws.comNS ns1.bluehost.com ldeger.com transposition A 185.244.151.84MX ldeger.comNS ns3.ro.hostsailor.com ldger.com omission A 13.248.169.48NS ns1.dan.com le.dger.com subdomain A 13.248.169.48NS ns5.afternic.com lecger.com replacement A 14.63.215.245NS ns1.hostname.net ledber.com replacement A 104.21.35.54NS chin.ns.cloudflare.com ledegr.com transposition A 185.244.151.84MX ledegr.comNS ns3.ro.hostsailor.com leder.com omission A 85.13.132.113MX w01a4668.kasserver.comNS ns5.kasserver.com ledg3r.com replacement NS ns1.dreamhost.com ledge.com omission A 54.215.31.113NS ns1.dyna-ns.net ledged.com replacement A 52.20.84.62NS ns1.atom.com ledgedr.com insertion A 31.43.160.6NS ns6.wixdns.net ledgee.com replacement A 13.248.169.48NS ns3.afternic.com ledgeer.com repetition A 52.20.84.62NS ns1.squadhelp.com ledgercom.com various A 91.215.86.207NS ns3.epik.com ledget.com replacement A 13.248.169.48NS ns1.afternic.com ledgewr.com insertion A 185.244.151.84MX ledgewr.comNS ns3.ro.hostsailor.com ledgger.com repetition A 13.56.33.8NS ns1.brandbucket.com ledgir.com vowel-swap A 188.114.96.3NS lynn.ns.cloudflare.com ledgor.com vowel-swap A 103.230.136.195MX mxn.mxhichina.comNS ens11.bigwww.com ledgr.com omission A 188.114.96.3NS kim.ns.cloudflare.com ledgre.com transposition A 172.65.185.109NS sp1.gname-dns.com ledgrer.com insertion A 185.244.151.84MX ledgrer.comNS ns3.ro.hostsailor.com ledgsr.com replacement A 14.63.215.245NS ns1.hostname.net ledgwer.com insertion A 185.244.151.84MX ledgwer.comNS ns3.ro.hostsailor.com ledgwr.com replacement A 185.244.151.84MX ledgwr.comNS ns3.ro.hostsailor.com ledher.com replacement A 15.197.148.33MX mailstore1.secureserver.netNS ns03.domaincontrol.com ledhger.com insertion A 185.244.151.84MX ledhger.comNS ns3.ro.hostsailor.com ledsger.com insertion A 185.244.151.84MX ledsger.comNS ns3.ro.hostsailor.com ledtger.com insertion A 188.114.96.3NS janet.ns.cloudflare.com ledyer.com replacement A 31.43.160.6MX alt1.aspmx.l.google.comNS ns-1051.awsdns-03.org ledzer.com replacement A 188.114.96.3NS kimora.ns.cloudflare.com leedger.com insertion MX mxbiz1.qq.comNS dns10.hichina.com legder.com transposition A 64.190.63.222MX localhostNS ns1.sedoparking.com leger.com omission A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com lerdger.com insertion A 185.244.151.84MX lerdger.comNS ns3.ro.hostsailor.com lerger.com replacement A 13.248.169.48NS ns1.afternic.com lesger.com replacement A 185.244.151.84MX lesger.comNS ns3.ro.hostsailor.com lewdger.com insertion A 185.244.151.84MX lewdger.comNS ns3.ro.hostsailor.com lidger.com vowel-swap A 66.241.124.184MX route1.mx.cloudflare.netNS erin.ns.cloudflare.com lledger.com repetition A 50.254.19.65MX lledger-com.mail.protection.outlook.comNS ns-1532.awsdns-63.org lodger.com vowel-swap A 149.210.148.65MX mail.lodger.comNS aron.ns.cloudflare.com lrdger.com replacement A 77.247.179.85MX mail.h-email.netNS ns1.badgerdns.com lsdger.com replacement A 14.63.215.245NS ns1.hostname.net oedger.com replacement A 14.63.215.245NS ns1.hostname.net pedger.com replacement A 74.220.199.6 pledger.com insertion A 216.40.34.37MX mx.netidentity.com.cust.hostedemail.comNS ns1.mailbank.com dedger.com bitsquatting MX aspmx1.migadu.comNS apollo.ns.cloudflare.com hedger.com bitsquatting A 15.197.225.128MX alt1.aspmx.l.google.comNS ns23.domaincontrol.com iedger.com homoglyph A 217.70.184.38MX fb.mail.gandi.netNS ns-157-c.gandi.net l-edger.com hyphenation A 216.198.79.65NS ns1.vercel-dns.com ladger.com bitsquatting A 185.80.2.134MX ladger.comNS ns209.superhosting.bg lcdlger.com homoglyph NS ns2.my-ndns.com lddger.com bitsquatting A 14.63.215.245NS ns1.hostname.net lebger.com homoglyph A 104.247.81.99NS ns1.parkingcrew.net leclger.com homoglyph A 34.42.100.71NS ns-cloud-e1.googledomains.com ledcer.com bitsquatting A 15.197.148.33MX ledcer-com.mail.protection.outlook.comNS pdns11.domaincontrol.com leddger.com insertion A 13.248.169.48NS ns1.afternic.com ledeer.com bitsquatting A 13.248.169.48NS ns1.dan.com ledeger.com insertion A 103.224.182.253MX park-mx.above.comNS ns1.abovedomains.com ledfer.com bitsquatting A 15.197.142.173MX mailstore1.secureserver.netNS ns11.domaincontrol.com ledg-er.com hyphenation A 162.255.119.245MX mail.protonmail.chNS dns1.registrar-servers.com ledgar.com bitsquatting A 13.248.169.48NS ns1.namefind.com ledger0.com addition A 20.82.12.44MX ledger0-com.mail.protection.outlook.comNS ns1-04.azure-dns.com ledger1.com addition A 44.232.173.249NS launch1.spaceship.net ledger4.com addition A 52.201.53.166NS nsg1.namebrightdns.com ledger5.com addition MX mail.protonmail.chNS ns-1175.awsdns-18.org ledger6.com addition A 52.20.84.62NS ns1.atom.com ledgerb.com addition A 91.195.240.82NS ns1dhl.name.com ledgerc.com addition A 198.185.159.144MX alt1.aspmx.l.google.comNS dns1.p02.nsone.net ledgerf.com addition A 94.75.193.73MX mail.h-email.netNS ns1.thednscloud.com ledgeri.com addition A 52.20.84.62NS ns1.atom.com ledgern.com addition A 192.0.78.162MX ledgern-com.mail.protection.outlook.comNS ns1.wordpress.com ledgerq.com addition A 31.43.160.6MX ledgerq-com.mail.protection.outlook.comNS ns03.domaincontrol.com ledgerx.com addition A 198.202.211.1MX usb-smtp-inbound-1.mimecast.comNS alla.ns.cloudflare.com ledges.com bitsquatting A 170.249.218.186MX ledges-com.mail.protection.outlook.comNS ns47.domaincontrol.com ledgez.com bitsquatting A 67.23.254.40MX ledgez.comNS ns1.reseller-228.mco2.hostdime.com ledgur.com bitsquatting A 13.248.243.5MX ledgur-com.mail.protection.outlook.comNS ns23.domaincontrol.com lediger.com homoglyph A 185.225.135.100MX mail02.lediger-consulting.deNS ns1.routing.net ledqer.com homoglyph A 13.223.25.84NS nsg1.namebrightdns.com leeger.com bitsquatting A 194.191.24.29MX alt1.aspmx.l.google.comNS cns1.cloudpit.de leelger.com homoglyph A 15.197.148.33NS ns69.domaincontrol.com lefger.com bitsquatting A 103.224.182.244MX park-mx.above.comNS ns1.abovedomains.com letger.com bitsquatting A 156.245.108.206NS ns1.dnsowl.com ludger.com bitsquatting A 18.195.62.85MX ludger-com.mail.protection.outlook.comNS ns11.worldnic.com

Showing 100 of 151

Check for cloaking

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

sol-incinerator-o3hbp6sam-solslugs.vercel.app

Evidence & External Reports

Security Analysis
URLScan Analyzed VirusTotal 2 det. ChainPatrol URLQuery Scamadviser 1 trust SSL Labs Stored certificate dates valid WOT 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.

Act on what you actually did. Entered a password: change it, and wherever you reused it. Paid or gave card details: contact your bank or payment service. Downloaded a file: scan the device. Then report the incident.

Immediate steps Find reporting contacts

Official reporting routes

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

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

IdentityTheft.gov United States

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

CISA United States

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

CSIRTs Network European Union

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

FIRST Worldwide

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

ReportCyber Australia

Report cybercrime to the Australian Cyber Security Centre and police.

Scamwatch Australia

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

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

Report to Your Local Authorities

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

If you made a payment, contact your bank or payment service through its official contacts as soon as possible. Keep the address, dates, payment or transaction details and messages for a report to the police or another competent authority. A report does not guarantee that money is returned.

Scammers are criminals. Filing a report creates a legal record and helps protect others.

97-country directory

Template-based draft • optional AI wording assistance requires separate consent

Review and submit it yourself
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Entered a password — change it on that service and on every other site where you used the same password
  • Turn on two-factor authentication — where the service offers it; an authenticator app is stronger than SMS codes
  • Paid or entered card or bank details — contact your bank or payment service through the contacts on your card or its official website

What information should I collect for my report?

FBI guidelines

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

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