Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
PhishDestroy forensic analysis flagged this domain. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
ledger----live.web.app favicon

ledger----live.web.app

In short

PhishDestroy stores a record for ledger----live.web.app. Source observations are dated separately; missing checks do not establish safety.

Review the evidence
Registrar
United StatesGoogle Domains
Resolved IP
United States199.36.158.100Fastly, 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
0 / 92
engine detections ·
URLScan
Malicious
Page captures
2
open gallery
Oct 22, 2026 CDN
X Telegram API
Source evidenceVirusTotal 0 / 92 6 sources

URLScan

Malicious

SHA-256 1dac1960226fe77014d977dc00b5633f4897120a6e79f19df16054a033c835c8

Open report
URLScanOriginal source recordObserved: 21 fields

Observed: · Retrieved:

Report ID

01a1653f-2818-7574-b786-9febb8441906

Final URL

https://ledger----live.web.app/

HTTP response

200

IP address

199.36.158.100

Contacted domains

  • ledger-wp-website-s3-prd.ledger.com
  • www.ledger.com
  • cdn.shopify.com
  • cdn.cookielaw.org
  • analytics.tiktok.com
  • kin.ledger.com
  • images.ctfassets.net
  • match.adsrvr.org
  • insight.adsrvr.org
  • www.google.com
  • bat.bing.com
  • t.teads.tv
  • js.adsrvr.org
  • s.yimg.com
  • t.contentsquare.net
  • bzrcdn.openai.com
  • fonts.gstatic.com
  • www.googletagmanager.com
  • cdnjs.cloudflare.com
  • cdn.optimizely.com
  • trc-events.taboola.com
  • pixel.rubiconproject.com
  • cm.g.doubleclick.net
  • ib.adnxs.com
  • bzr.openai.com
  • www.facebook.com
  • www.google.ca
  • googleads.g.doubleclick.net
  • analytics-ipv6.tiktokw.us
  • cm.teads.tv

Contacted IP addresses

  • 141.226.230.48
  • 216.19.192.2
  • 68.67.160.76
  • 3.33.220.150
  • 172.64.151.22
  • 157.240.241.35
  • 142.250.31.94
  • 172.253.63.155
  • 23.210.73.86
  • 151.101.2.132
  • 151.101.194.132
  • 54.160.143.175
  • 104.18.34.152
  • 162.159.140.229
  • 172.66.0.227

Autonomous systems (ASN)

  • 200478
  • 26667
  • 29990
  • 16509
  • 13335
  • 32934
  • 15169
  • 20940
  • 54113
  • 14618

Server countries

  • US
  • DE
  • CA
  • IE

Linked domains

  • cookiepedia.co.uk
  • www.onetrust.com

Document hash

0008c37b519eee5fe324a7340b27cb9db3265ee239f1deecc1f6fea1bb1ed0d9

JavaScript globals

  • getCookie
  • consentState
  • optimizely
  • _wpemojiSettings
  • wpml_cookies
  • OneTrustStub
  • jQuery
  • dataLayer
  • r
  • m
  • onRecaptchaEnterpriseApiLoaded
  • heateorSssLoadEvent
  • heateorSssSharingAjaxUrl
  • heateorSssCloseIconPath
  • heateorSssPluginIconPath
  • heateorSssHorizontalSharingCountEnable
  • heateorSssVerticalSharingCountEnable
  • heateorSssSharingOffset
  • heateorSssMobileStickySharingEnabled
  • heateorSssCopyLinkMessage
  • heateorSssUrlCountFetched
  • heateorSssSharesText
  • heateorSssShareText
  • heateorSssPopup
  • heateorSssDetermineWhatsappShareAPI
  • heateorSssMoreSharingPopup
  • heateorSssMastodonPopup
  • heateorSssFilterSharing
  • heateorSssFacebookTargetUrls
  • heateorSssGetSharingCounts
  • heateorSssFetchFacebookShares
  • heateorSssFBShareJSONCall
  • heateorSssSaveFacebookShares
  • heateorSssCalculateApproxCount
  • heateorSssCalculateActualCount
  • heateorSssCapitaliseFirstLetter
  • heateorSssHideSharing
  • ClipboardJS
  • phpVariables
  • ParamsDataMain

Cookies

  • taboola_session_id
  • __cf_bm
  • wp-wpml_current_language
  • _gcl_au
  • _cfuvid
  • _rdt_uuid
  • __obref
  • _twsid
  • _twpid
  • guest_id_marketing
  • guest_id_ads
  • personalization_id
  • guest_id
  • muc_ads
  • _ttp
  • _ga
  • _uetsid
  • _uetvid
  • t_gid
  • t_pt_gid

Browser storage keys

  • wpEmojiSettingsSupports
  • _gcl_ls
  • _rdt_cfg
  • first_fifty_cryptos
  • _taboolaStorageDetection
  • taboolaStorageDetection
  • eng_mt
  • _uetsid
  • _uetsid_exp
  • _uetvid
  • _uetvid_exp
  • taboola global:user-id
  • 1893020:session-data
  • tt_sessionId
  • tt_pixel_session_index

TLS session and certificate

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

Domain age, days

128

Registered domain age, days

128

Certificate age, days

29

Certificate validity, days

89

Page requests

189

Provider verdicts

Engine verdict
Tags
  • urlscan-ml
  • urlscan-ml-60c5e22
Score
97
Malicious
Yes
Overall verdict
Tags
  • phishing
Score
100
Brands
  • ledger
Malicious
Yes
Categories
  • phishing
URLScan verdict
Tags
  • phishing
Score
100
Brands
  • Ledger
Malicious
Yes
Categories
  • phishing

HTTP headers

Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Uuid
01a1653f-2818-7574-b786-9febb8441906
Final url
https://ledger----live.web.app/
Status
200
Ip
199.36.158.100
Contacted domains
[
    "ledger-wp-website-s3-prd.ledger.com",
    "www.ledger.com",
    "cdn.shopify.com",
    "cdn.cookielaw.org",
    "analytics.tiktok.com",
    "kin.ledger.com",
    "images.ctfassets.net",
    "match.adsrvr.org",
    "insight.adsrvr.org",
    "www.google.com",
    "bat.bing.com",
    "t.teads.tv",
    "js.adsrvr.org",
    "s.yimg.com",
    "t.contentsquare.net",
    "bzrcdn.openai.com",
    "fonts.gstatic.com",
    "www.googletagmanager.com",
    "cdnjs.cloudflare.com",
    "cdn.optimizely.com",
    "trc-events.taboola.com",
    "pixel.rubiconproject.com",
    "cm.g.doubleclick.net",
    "ib.adnxs.com",
    "bzr.openai.com",
    "www.facebook.com",
    "www.google.ca",
    "googleads.g.doubleclick.net",
    "analytics-ipv6.tiktokw.us",
    "cm.teads.tv"
]
Contacted IP addresses
[
    "141.226.230.48",
    "216.19.192.2",
    "68.67.160.76",
    "3.33.220.150",
    "172.64.151.22",
    "157.240.241.35",
    "142.250.31.94",
    "172.253.63.155",
    "23.210.73.86",
    "151.101.2.132",
    "151.101.194.132",
    "54.160.143.175",
    "104.18.34.152",
    "162.159.140.229",
    "172.66.0.227"
]
Asns
[
    "200478",
    "26667",
    "29990",
    "16509",
    "13335",
    "32934",
    "15169",
    "20940",
    "54113",
    "14618"
]
Countries
[
    "US",
    "DE",
    "CA",
    "IE"
]
Linked domains
[
    "cookiepedia.co.uk",
    "www.onetrust.com"
]
Document hash
0008c37b519eee5fe324a7340b27cb9db3265ee239f1deecc1f6fea1bb1ed0d9
Globals
[
    "getCookie",
    "consentState",
    "optimizely",
    "_wpemojiSettings",
    "wpml_cookies",
    "OneTrustStub",
    "jQuery",
    "dataLayer",
    "r",
    "m",
    "onRecaptchaEnterpriseApiLoaded",
    "heateorSssLoadEvent",
    "heateorSssSharingAjaxUrl",
    "heateorSssCloseIconPath",
    "heateorSssPluginIconPath",
    "heateorSssHorizontalSharingCountEnable",
    "heateorSssVerticalSharingCountEnable",
    "heateorSssSharingOffset",
    "heateorSssMobileStickySharingEnabled",
    "heateorSssCopyLinkMessage",
    "heateorSssUrlCountFetched",
    "heateorSssSharesText",
    "heateorSssShareText",
    "heateorSssPopup",
    "heateorSssDetermineWhatsappShareAPI",
    "heateorSssMoreSharingPopup",
    "heateorSssMastodonPopup",
    "heateorSssFilterSharing",
    "heateorSssFacebookTargetUrls",
    "heateorSssGetSharingCounts",
    "heateorSssFetchFacebookShares",
    "heateorSssFBShareJSONCall",
    "heateorSssSaveFacebookShares",
    "heateorSssCalculateApproxCount",
    "heateorSssCalculateActualCount",
    "heateorSssCapitaliseFirstLetter",
    "heateorSssHideSharing",
    "ClipboardJS",
    "phpVariables",
    "ParamsDataMain"
]
Cookies
[
    "taboola_session_id",
    "__cf_bm",
    "wp-wpml_current_language",
    "_gcl_au",
    "_cfuvid",
    "_rdt_uuid",
    "__obref",
    "_twsid",
    "_twpid",
    "guest_id_marketing",
    "guest_id_ads",
    "personalization_id",
    "guest_id",
    "muc_ads",
    "_ttp",
    "_ga",
    "_uetsid",
    "_uetvid",
    "t_gid",
    "t_pt_gid"
]
Storage keys
[
    "wpEmojiSettingsSupports",
    "_gcl_ls",
    "_rdt_cfg",
    "first_fifty_cryptos",
    "_taboolaStorageDetection",
    "taboolaStorageDetection",
    "eng_mt",
    "_uetsid",
    "_uetsid_exp",
    "_uetvid",
    "_uetvid_exp",
    "taboola global:user-id",
    "1893020:session-data",
    "tt_sessionId",
    "tt_pixel_session_index"
]
Tls
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR4",
    "subject": "web.app",
    "protocol": "TLS 1.3",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Domain age days
128
Apex age days
128
Tls age days
29
Tls valid days
89
Requests
189
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 97,
        "malicious": true
    },
    "overall": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "ledger"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    },
    "urlscan": {
        "tags": [
            "phishing"
        ],
        "score": 100,
        "brands": [
            "Ledger"
        ],
        "malicious": true,
        "categories": [
            "phishing"
        ]
    }
}
HTTP headers
{
    "content-type": "text/html; charset=utf-8",
    "strict-transport-security": "max-age=31556926; 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
01a1653f-2818-7574-b786-9febb8441906
score
100
malicious
true
result_at
2026-10-23T03:30:45Z
enriched_at
2026-10-23T08:21:41Z
source_timestamps
{"urlscan_result_at":"2026-10-23 05:30:45","urlscan_enriched_at":"2026-10-23 10:21:41"}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

VirusTotal

0 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 13 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
56
Malicious
0
Suspicious
0
Undetected
36

Reputation score

0

Tags

  • dga

Registrar

MarkMonitor Inc.

Created

Expires

Updated

First seen

DNS records

  • TTL, seconds
    21600
    Type
    AAAA
    Value
    2620:0:890::100
  • TTL, seconds
    21600
    Type
    A
    Value
    199.36.158.100

DNS records observed

JARM fingerprint

29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c

Certificate

Subject alternative names
  • web.app
  • *.web.app
Issuer
Google Trust Services / WR4
Serial
e26d762a101120cd12a8f68d86c31d05
SHA-256
7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Subject
web.app
Valid until
Valid from

Registration record

Registrar
MarkMonitor Inc.
Registrar IANA ID
292
Registrar URL
http://www.markmonitor.com
Registered
Updated
Expires
Status
  • clientDeleteProhibited
  • clientTransferProhibited
  • clientUpdateProhibited
Nameservers
  • ns1.googledomains.com
  • ns2.googledomains.com
  • ns3.googledomains.com
  • ns4.googledomains.com
DNSSEC
unsigned
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 56,
    "malicious": 0,
    "suspicious": 0,
    "undetected": 36
}
Reputation
0
Tags
[
    "dga"
]
Registrar
MarkMonitor Inc.
Created
2019-01-08T22:05:04Z
Expires
2026-01-08T22:05:04Z
Updated
2024-12-12T10:14:49Z
First seen
2026-05-18T07:26:24Z
DNS records
[
    {
        "ttl": 21600,
        "type": "AAAA",
        "value": "2620:0:890::100"
    },
    {
        "ttl": 21600,
        "type": "A",
        "value": "199.36.158.100"
    }
]
Dns at
2026-10-22T20:36:30Z
Jarm
29d3fd00029d29d00041d41d00041d6b5eefa2404a56c2ced79a0d16afe36c
Certificate
{
    "san": [
        "web.app",
        "*.web.app"
    ],
    "issuer": "Google Trust Services / WR4",
    "serial": "e26d762a101120cd12a8f68d86c31d05",
    "sha256": "7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095",
    "subject": "web.app",
    "valid_to": "2026-12-22T17:59:57Z",
    "valid_from": "2026-09-23T17:59:58Z"
}
Registration record
{
    "registrar": "MarkMonitor Inc.",
    "registrar_iana_id": "292",
    "registrar_url": "http://www.markmonitor.com",
    "created": "2019-01-08T22:05:04Z",
    "updated": "2024-12-12T10:14:49Z",
    "expires": "2026-01-08T22:05:04Z",
    "status": [
        "clientDeleteProhibited",
        "clientTransferProhibited",
        "clientUpdateProhibited"
    ],
    "nameservers": [
        "ns1.googledomains.com",
        "ns2.googledomains.com",
        "ns3.googledomains.com",
        "ns4.googledomains.com"
    ],
    "dnssec": "unsigned"
}
Separate source record · 0 malicious + 0 suspicious / 92 · 2026-10-22 20:31:04 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-22T20:31:04Z
fetched_at
2026-10-22T20:38:41Z
stats
{"timeout":0,"harmless":56,"malicious":0,"suspicious":0,"undetected":36}

OTX

no community references

Open report

Google Safe Browsing

No threat flag

Open report

Spamhaus DBL

Check recorded; verdict not retained

Open report

PhishDestroy DOM

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

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

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:24Z
source_timestamp
2026-10-23 00:20:24
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: 14 fields

Mail configuration

SPF lookups
0

CAA records

Count
1
Domain
web.app
Allowed issuers
  • pki.goog

Protective DNS results

Resolvers checked
12
Blocking resolvers
0

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

DNS servers

Nameservers
  • IP address
    216.239.34.99
    Host
    ns2.googledomains.com
  • IP address
    216.239.32.99
    Host
    ns1.googledomains.com
  • IP address
    216.239.38.99
    Host
    ns4.googledomains.com
  • IP address
    216.239.36.99
    Host
    ns3.googledomains.com
DNS zone
web.app

Location

IP address
2620:0:890::100
ASN
54113
Organization
Fastly, Inc.
City
Mountain View
Country
US

TLS certificate

Issuer
Google Trust Services / WR4
Subject
web.app

DNS records

A
  • 199.36.158.100
AAAA
  • 2620:0:890::100

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

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

IP lookup

IP address
2620:0:890::100
IP version
6

HTTP headers

Response headers
Content-type
text/html; charset=utf-8
Strict-transport-security
max-age=31556926; includeSubDomains; preload
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "count": 1,
    "domain": "web.app",
    "issuers": [
        "pki.goog"
    ]
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_count": 0
}
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
    ]
}
Dns server
{
    "ns": [
        {
            "ip": "216.239.34.99",
            "host": "ns2.googledomains.com"
        },
        {
            "ip": "216.239.32.99",
            "host": "ns1.googledomains.com"
        },
        {
            "ip": "216.239.38.99",
            "host": "ns4.googledomains.com"
        },
        {
            "ip": "216.239.36.99",
            "host": "ns3.googledomains.com"
        }
    ],
    "zone": "web.app"
}
Location
{
    "ip": "2620:0:890::100",
    "asn": "54113",
    "org": "Fastly, Inc.",
    "city": "Mountain View",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR4",
    "subject": "web.app"
}
DNS records
{
    "A": [
        "199.36.158.100"
    ],
    "AAAA": [
        "2620:0:890::100"
    ]
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "header": "max-age=31556926; 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=31556926; includeSubDomains; preload",
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "2620:0:890::100",
    "family": 6
}
HTTP headers
{
    "headers": {
        "content-type": "text/html; charset=utf-8",
        "strict-transport-security": "max-age=31556926; includeSubDomains; preload"
    }
}

Explore

Blocklist matchesPhishDestroy · no match in the other 11 1
PhishDestroy PhishDestroy list View source

Checked, no match

Last checked

Stored Capture · 2 captures

Primary capture 1 / 2
SourcePrimary capture
Recorded
StateStored capture
Position1 / 2
Open capture Wayback Download
All capture links and hashes (2)
ledger----live.web.app: Suspected Ledger impersonation — 12/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical).
Social preview card ledger----live.web.app: Suspected Ledger impersonation — 12/92 VirusTotal engines. PhishDestroy risk score 100/100 (critical). v cb12f6ac221f

Domain details

Domain
URLScan verdict Malicious score 100 Phishing brand: Ledger report ↗
IP Context United States199.36.158.100 Cloudflare shared edge origin IP hidden Edge-IP reputation is not attributed to this domain.
Platform provider Google Domains US(US)
Abuse contactnetwork-abuse@google.com, cloud-abuse@google.com
HTTP Status301 Moved Permanently
Technical detailsProvenance & timestamps
First DetectedOct 22, 2026
DOM Analysisanalyzed Oct 23, 2026score 100/1005 brand signals
Submitted URLhttps://ledger----live.web.app/
Favicon Hash
Observed page title
Site Not Found
Automated brand references
Ankr Ethereum Google Ledger Solana
TLS Certificate
Issued by WR4 · stored validity ends in 51 days

Network & certificates

Stored technical evidence

Network & DNS

Shared CDN edge
Resolved IP
United States199.36.158.100
Network ASN
AS54113
AS name
FASTLY - Fastly, Inc., US
Organization
Fastly, Inc.
Observed location
United StatesMountain View, US
Server header
cloudflare

Edge-IP reputation is not attributed to this domain.

Location describes the IP network.

TLS certificate

Issuer
WR4
Valid from
2026-09-23 17:59:58
Valid until
2026-12-22 17:59:57
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprint7175912cef4e9b3d3f320d60e4e926f7cb6a2f624028de25218038a3f679e095
Certificate names · 2 SANs
  • web.app
  • *.web.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 · 199.36.158.100rapiddns.io

Latest Classified Outcome 2026-10-31 23:12:06 UTC

The site was redirecting visitors elsewhere at the latest check.

Technical details
Primary outcome Redirecting reason: HTTP redirect observed 80% confidence
Attribution source: Current Http Probe
Evidence layers Availability: Redirecting Content: Unknown DNS: Stale Registration: Unknown
Latest HTTP observation Redirecting HTTP redirect observed 80% 2026-10-31 23:12:06 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 23:12:06 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
Registration & observation details2

Availability observations

Last reachable 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: 189 SHA-256 hashes: 180 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:02 UTC.

Open this scan on URLScan 01a1653f-2818-7574-b786-9febb8441906 ↗

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

    redirected

    http_redirect

  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_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:12:06.000000
    Evidence SHA-256
    0b06c2b7f687da9326c157df62e391342d0c571a56f92bbf1f6c739990e4197e
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:12:06
    Evidence reason
    redirect
  2. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-11-01 00:12:06.000000
    Evidence SHA-256
    0b06c2b7f687da9326c157df62e391342d0c571a56f92bbf1f6c739990e4197e
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-11-01 00:12:06
    Evidence reason
    redirect
  3. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:12:52.000000
    Evidence SHA-256
    a0c59ed030a32477fb2bc170be37d6622251201cd955de27dfd82b8d7f59e3dd
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 12:12:52
    Evidence reason
    redirect
  4. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 12:12:52.000000
    Evidence SHA-256
    a0c59ed030a32477fb2bc170be37d6622251201cd955de27dfd82b8d7f59e3dd
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 12:12:52
    Evidence reason
    redirect
  5. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:33:58.000000
    Evidence SHA-256
    0e826b0b17ee1276c88e4ad7b8a7f3a10d6092d3980e887013c3af491ab6d163
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 03:33:58
    Evidence reason
    redirect
  6. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 03:33:58.000000
    Evidence SHA-256
    0e826b0b17ee1276c88e4ad7b8a7f3a10d6092d3980e887013c3af491ab6d163
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-31 03:33:58
    Evidence reason
    redirect
  7. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:10:41.000000
    Evidence SHA-256
    bb2eaa6e6854c84269792f5d405fd91473611a0b75c78f778cdbaee7ac4c53b4
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 12:10:41
    Evidence reason
    redirect
  8. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 12:10:41.000000
    Evidence SHA-256
    bb2eaa6e6854c84269792f5d405fd91473611a0b75c78f778cdbaee7ac4c53b4
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 12:10:41
    Evidence reason
    redirect
  9. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:10:42.000000
    Evidence SHA-256
    a5eab45e76b31309aa547e2381927ff37e564c65d136aa6fb2e81cbdcc67fea4
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 00:10:42
    Evidence reason
    redirect
  10. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-30 00:10:42.000000
    Evidence SHA-256
    a5eab45e76b31309aa547e2381927ff37e564c65d136aa6fb2e81cbdcc67fea4
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-30 00:10:42
    Evidence reason
    redirect
  11. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:11:14.000000
    Evidence SHA-256
    abcc68194ab40169bb43394c0aea184492d3892119991aee725233e062a5c45b
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-29 12:11:14
    Evidence reason
    redirect
  12. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 12:11:14.000000
    Evidence SHA-256
    abcc68194ab40169bb43394c0aea184492d3892119991aee725233e062a5c45b
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-29 12:11:14
    Evidence reason
    redirect
  13. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:39:55.000000
    Evidence SHA-256
    df59b2190dd21a13fa6680157050385b7ff12c01e845698b6ac2ee6ed68657ec
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-29 03:39:55
    Evidence reason
    redirect
  14. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-29 03:39:55.000000
    Evidence SHA-256
    df59b2190dd21a13fa6680157050385b7ff12c01e845698b6ac2ee6ed68657ec
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-29 03:39:55
    Evidence reason
    redirect
  15. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:18.000000
    Evidence SHA-256
    a11893b5caf3cf455513deb0e4a1ac4b79a0b6604e3c9c3c7feae9770b8a4000
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-28 12:06:18
    Evidence reason
    redirect
  16. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 12:06:18.000000
    Evidence SHA-256
    a11893b5caf3cf455513deb0e4a1ac4b79a0b6604e3c9c3c7feae9770b8a4000
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-28 12:06:18
    Evidence reason
    redirect
  17. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:06:47.000000
    Evidence SHA-256
    773a2bf588db70e896f4260c71ab61579ccdf51db06e82acc3ba420a10398467
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-28 00:06:47
    Evidence reason
    redirect
  18. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-28 00:06:47.000000
    Evidence SHA-256
    773a2bf588db70e896f4260c71ab61579ccdf51db06e82acc3ba420a10398467
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-28 00:06:47
    Evidence reason
    redirect
  19. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:06:34.000000
    Evidence SHA-256
    d4a6b11a1e9072559d76a66ca54576d6a204fe9bb5de4bd3f9be31e1e3e0954d
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-27 12:06:34
    Evidence reason
    redirect
  20. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-27 12:06:34.000000
    Evidence SHA-256
    d4a6b11a1e9072559d76a66ca54576d6a204fe9bb5de4bd3f9be31e1e3e0954d
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-27 12:06:34
    Evidence reason
    redirect
  21. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:01:34.000000
    Evidence SHA-256
    ab0a041d8a788f8e97efd8d6ddf35bb1d3260742c4b281098a7cf2daaa6642ac
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 12:01:34
    Evidence reason
    redirect
  22. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 12:01:34.000000
    Evidence SHA-256
    ab0a041d8a788f8e97efd8d6ddf35bb1d3260742c4b281098a7cf2daaa6642ac
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 12:01:34
    Evidence reason
    redirect
  23. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:01:50.000000
    Evidence SHA-256
    0a5179d909c114409a3bdbce04a53d857c6de583b2fe142cd146f33dad6e7264
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 00:01:50
    Evidence reason
    redirect
  24. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-26 00:01:50.000000
    Evidence SHA-256
    0a5179d909c114409a3bdbce04a53d857c6de583b2fe142cd146f33dad6e7264
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-26 00:01:50
    Evidence reason
    redirect
  25. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:01:58.000000
    Evidence SHA-256
    360f4b12ef96211455ca465336b46acd1c842a14244f86a6a2e8046df184d7cf
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 12:01:58
    Evidence reason
    redirect
  26. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 12:01:58.000000
    Evidence SHA-256
    360f4b12ef96211455ca465336b46acd1c842a14244f86a6a2e8046df184d7cf
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 12:01:58
    Evidence reason
    redirect
  27. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:54:39.000000
    Evidence SHA-256
    cbed14cc27bc5870f45c0e15d242bc821200ae6e5f5d882adf794c050ff50f26
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 03:54:39
    Evidence reason
    redirect
  28. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-25 03:54:39.000000
    Evidence SHA-256
    cbed14cc27bc5870f45c0e15d242bc821200ae6e5f5d882adf794c050ff50f26
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-25 03:54:39
    Evidence reason
    redirect
  29. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:00:41.000000
    Evidence SHA-256
    96c331f0bdaecff56c544fe89813b5dc245617317040eeb1061672411c0ee00f
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 12:00:41
    Evidence reason
    redirect
  30. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 12:00:41.000000
    Evidence SHA-256
    96c331f0bdaecff56c544fe89813b5dc245617317040eeb1061672411c0ee00f
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 12:00:41
    Evidence reason
    redirect
  31. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:00:50.000000
    Evidence SHA-256
    126ea1d8a8b24e70bd75a5be0e14e7b9121a6a2d7fdbbbd28016a66a3dcbd9d0
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 00:00:50
    Evidence reason
    redirect
  32. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-24 00:00:50.000000
    Evidence SHA-256
    126ea1d8a8b24e70bd75a5be0e14e7b9121a6a2d7fdbbbd28016a66a3dcbd9d0
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-24 00:00:50
    Evidence reason
    redirect
  33. current_http_proberedirected
    Observation source
    current_http_probe
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    stale
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:00:42.000000
    Evidence SHA-256
    4c1d540921e64e61a90744b0f6692e061b2ee8049d52f854edf66344b7232a33
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 12:00:42
    Evidence reason
    redirect
  34. http_observationredirected
    Observation source
    http_observation
    Cause
    http_redirect
    Availability state
    reachable_redirect
    Content state
    unknown
    DNS state
    unknown
    Recorded HTTP status
    301
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    80
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-23 12:00:42.000000
    Evidence SHA-256
    4c1d540921e64e61a90744b0f6692e061b2ee8049d52f854edf66344b7232a33
    HTTP probe value as recorded
    301
    Evidence timestamp as recorded
    2026-10-23 12:00:42
    Evidence reason
    redirect
  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 22:14:46.000000
    Evidence SHA-256
    e33cfefa5cd46628efc84ff2a36b91bd8b0c1df81364ee6135236f3fe407d740
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 22:14:46
    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 22:14:46.000000
    Evidence SHA-256
    e33cfefa5cd46628efc84ff2a36b91bd8b0c1df81364ee6135236f3fe407d740
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-22 22:14:46
    Evidence reason

Threat Response Pipeline

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

Recorded events: 7. 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
    ledger----live.web.app detected and queued for full analysis
Threat Intelligence ChecksURLScan.io Capture · URLScan Verdict · Automated brand label: Ledger · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 5 of 5
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan classified the page as malicious · Score: 100
  • 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

3 entries
  1. VirusTotal

    0/92 engine detections

    View source
  2. Added to PhishDestroy

    ledger----live.web.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

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.

ledger----live.web.app

Evidence & External Reports

Security Analysis
URLScan Malicious VirusTotal ChainPatrol URLQuery 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?

2 evidence signal groups linked Last known active
You are not alone and there is nothing to be ashamed of. Scammers are sophisticated criminals who exploit trust. Reporting your experience is the most powerful weapon against fraud — your report can prevent others from becoming victims and help law enforcement take action. Silence is the scammer’s greatest advantage. Break it.
If credentials were compromised, report immediately. Do not engage with recovery scammers.

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

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 ledger----live.web.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/ledger----live.web.app"
  title="PhishDestroy threat report for ledger----live.web.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>