Security engines reporting a detection: 1. Public blocklists reporting a match: 1. Exercise extreme caution — do not enter credentials or personal information.
Analysis of the domain listas.claims shows multiple indicators of malicious activity consistent with a crypto‑draining scam. The site was registered on February 21, 2026 and is presently taken offline, but historical data remain relevant for threat‑hunting. DNS resolution points to IP address 216.198.79.1, which geolocates to the United States and is owned by Lefkoff Industries. The hosting infrastructure does not appear to be shared with legitimate services, raising the likelihood of a dedicated malicious server.
The SSL certificate presented by the site is identified as R13, a certificate that lacks a recognized public‑trust chain and is commonly observed on fraudulent domains. The page title returned from the site is "$LISTA Airdrop," and the underlying code matches the publicly catalogued Airdrop Scam phishing kit, confirming the use of a known airdrop‑themed lure to entice cryptocurrency victims. VirusTotal analysis records a single positive detection out of 93 scanning engines, indicating at least one vendor has identified malicious behavior. Independent blocklist feeds list the domain on two security blocklists, and it has been explicitly blocked by the PhishDestroy and ScamSniffer filtering services.
These multiple independent detections reinforce the assessment that the domain is part of a coordinated crypto‑drain operation. Defenders should continue to block listas.claims at the DNS and proxy layers, monitor outbound connections to its resolved IP, and flag any internal traffic that attempts TLS handshakes with the R13 certificate. Since the site is currently offline, threat actors may re‑host the payload elsewhere; therefore, security teams should also watch for the Airdrop Scam kit signatures and similar page titles in future incidents. Continuous re‑query of VirusTotal and blocklist sources is advised to capture any new detections that could indicate re‑activation of the infrastructure.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo crawler-versus-browser difference has been recorded yet
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
Stored cloaking flag
Not yet scanned
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='listas.claims', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
IP ContextVercel shared edgeorigin IP hiddenEdge-IP reputation is not attributed to this domain.
RegistrationCreated Feb 21, 2026 (234d)
Time to First Unavailability132 days
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedFeb 26, 2026
DOM Analysisanalyzed Jul 29, 2026score 56/10010 brand signals
Edge-IP reputation is not attributed to this domain.
Location describes the IP network.
TLS certificate
Issuer
R13
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:10:22 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-03-16 17:05:06 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-16 17:05:06 UTC → 2026-09-30 16:14:55 UTC · 4,751.16hmidpoint estimate ≈ 2026-06-23 16:40:00 UTC · precision very low · basis bounded
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
listas.claims detected and queued for full analysis
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Mar 17, 2026
Time to First Unavailability
3170 hours elapsed from detection to the first unavailable observation.
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+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
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.
4 evidence signal groups linked0 reports recordedContent unavailable
If credentials were compromised, report immediately. Do not engage with recovery scammers.
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
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 →
Template-based draft · optional AI wording assistance requires separate consent
Template-based draft • optional AI wording assistance requires separate consent · Review and submit it yourself
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · listas.claims
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches1
Same favicon hash or the same page title as this host.
