Skip to security report
Analytics Dashboard
This domain has been flagged as malicious
Security engines reporting a detection: 17. Exercise extreme caution — do not enter credentials or personal information.
Were you scammed by this site?Report to authorities
Domain security and threat intelligence
luntle-thrum.shop favicon

luntle-thrum.shop

In short

PhishDestroy records luntle-thrum.shop as a Polish-language page asking visitors to enter a password and confirm it.

“ostrzeżenie - H***a”

Review the evidence
Registrar
United StatesSpaceship
Resolved IP
United States34.8.77.192Google LLC
Registered
Oct 15, 2026
First observed
Oct 31, 2026
PhishDestroy assessment Critical
100/100
Evidence score
Availability Last known active Latest stored reachability observation Observed HTTP probe
Risk signals
VirusTotal detections: 17/92 Spamhaus DBL: phishing domain Young domain: 17 days old
VirusTotal
17 / 92
engine detections ·
OTX
3
community references
URLScan
Malicious
engine verdict · score 91
Page captures
6
open gallery
Domain age
17 days
registered 2026-10-15 according to WHOIS
OTX: 3 refs Oct 31, 2026
X Telegram API

Analysis

Domain summary

PhishDestroy records luntle-thrum.shop as a Polish-language page asking visitors to enter a password and confirm it.

Critical
Status
Last known active
VirusTotal
17 / 92
Hosting
United States34.8.77.192Google LLC
Registrar
United StatesSpaceship
Registered
Oct 15, 2026
OTX
3 community refs
Page captures
6
Page captures Source results Registration record

PhishDestroy analysis, reviewed version

The captured page on luntle-thrum.shop presents a single centered prompt in Polish: a masked heading reading "H***a", a text field with the placeholder "Proszę podać hasło" (please enter the password), and a brown button labeled "potwierdzić" (confirm). The HTML title "ostrzeżenie - H***a" (warning) frames the page as a warning screen, yet the visible content offers no explanation of what is being warned about — only the password request. The layout is otherwise empty, with no branding, links, or supporting text visible in the capture.

The stored VirusTotal domain result reports 17 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".

Source evidenceVirusTotal 17 / 92 · OTX 3 references 8 sources

VirusTotal

17 / 92 engine detections · stored summary

Open report
VirusTotalOriginal source recordObserved: 9 fields

Observed: · Retrieved:

Vendor result counts

Timeout
0
Harmless
43
Malicious
14
Suspicious
3
Undetected
32

Vendor labels

CRDF
malicious
DNS8
suspicious
ESET
suspicious
VIPRE
malware
G-Data
phishing
Lionic
phishing
Sophos
phishing
Fortinet
phishing
PREBYTES
phishing
SOCRadar
phishing
Kaspersky
phishing
LevelBlue
phishing
Seclookup
malicious
Gridinsoft
suspicious
BitDefender
phishing
alphaMountain.ai
phishing
Forcepoint ThreatSeeker
phishing

Reputation score

0

Categories

alphaMountain.ai
Phishing (alphaMountain.ai)

First seen

DNS records

  • TTL, seconds
    21600
    Type
    NS
    Value
    ns2.dnsip.com
  • TTL, seconds
    600
    Type
    A
    Value
    34.8.77.192
  • TTL, seconds
    21600
    Type
    NS
    Value
    ns1.dnsip.com
  • TTL, seconds
    600
    Type
    SOA
    Responsible mailbox
    dnsadmin.dnsip.com
    Value
    ns1.dnsip.com

DNS records observed

JARM fingerprint

29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84

Certificate

Subject alternative names
  • luntle-thrum.shop
Issuer
Google Trust Services / WR3
Serial
60e7e17bb8ec0a721010445bd7a5ecca
SHA-256
f0b2b7bfb3c8e61c366c4f4ab55c870356a8ef79483fb4e78285c1a209df96d0
Subject
luntle-thrum.shop
Valid until
Valid from
Original source fields · JSON
Vendor result counts
{
    "timeout": 0,
    "harmless": 43,
    "malicious": 14,
    "suspicious": 3,
    "undetected": 32
}
Vendor labels
{
    "CRDF": "malicious",
    "DNS8": "suspicious",
    "ESET": "suspicious",
    "VIPRE": "malware",
    "G-Data": "phishing",
    "Lionic": "phishing",
    "Sophos": "phishing",
    "Fortinet": "phishing",
    "PREBYTES": "phishing",
    "SOCRadar": "phishing",
    "Kaspersky": "phishing",
    "LevelBlue": "phishing",
    "Seclookup": "malicious",
    "Gridinsoft": "suspicious",
    "BitDefender": "phishing",
    "alphaMountain.ai": "phishing",
    "Forcepoint ThreatSeeker": "phishing"
}
Reputation
0
Categories
{
    "alphaMountain.ai": "Phishing (alphaMountain.ai)"
}
First seen
2026-10-15T08:26:11Z
DNS records
[
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns2.dnsip.com"
    },
    {
        "ttl": 600,
        "type": "A",
        "value": "34.8.77.192"
    },
    {
        "ttl": 21600,
        "type": "NS",
        "value": "ns1.dnsip.com"
    },
    {
        "ttl": 600,
        "type": "SOA",
        "rname": "dnsadmin.dnsip.com",
        "value": "ns1.dnsip.com"
    }
]
Dns at
2026-10-25T09:25:03Z
Jarm
29d3fd00029d29d00042d43d00041d6f940079659edb62e1c38c38bd26ee84
Certificate
{
    "san": [
        "luntle-thrum.shop"
    ],
    "issuer": "Google Trust Services / WR3",
    "serial": "60e7e17bb8ec0a721010445bd7a5ecca",
    "sha256": "f0b2b7bfb3c8e61c366c4f4ab55c870356a8ef79483fb4e78285c1a209df96d0",
    "subject": "luntle-thrum.shop",
    "valid_to": "2027-01-13T04:30:32Z",
    "valid_from": "2026-10-15T03:35:59Z"
}
Separate source record · 14 malicious + 3 suspicious / 92 · 2026-10-25 09:19:38 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-25T09:19:38Z
fetched_at
2026-10-31T11:15:21Z
stats
{"timeout":0,"harmless":43,"malicious":14,"suspicious":3,"undetected":32}

Spamhaus DBL

phishing domain

URLScan

Malicious · engine verdict · score 91

SHA-256 6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d

Open report
URLScanOriginal source recordObserved: 19 fields

Observed: · Retrieved:

Report ID

01a191b3-a9d8-74df-be7e-95e1ce37eb3a

Final URL

https://luntle-thrum.shop/

HTTP response

200

Redirect type

https-only

Redirects

  • To
    https://luntle-thrum.shop/
    From
    http://luntle-thrum.shop/
    Status
    307

IP address

34.8.77.192

Reverse DNS (PTR)

192.77.8.34.bc.googleusercontent.com

Contacted IP addresses

  • 34.8.77.192

Autonomous systems (ASN)

  • 396982

Server countries

  • US

Document hash

6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d

TLS session and certificate

Subject alternative names
  • luntle-thrum.shop
Cipher
AES_128_GCM
Issuer
WR3
Subject
luntle-thrum.shop
Protocol
TLS 1.3
Valid until
Valid from

Domain age, days

16

Registered domain age, days

16

Certificate age, days

16

Certificate validity, days

90

Page requests

2

Provider verdicts

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

HTTP headers

Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Uuid
01a191b3-a9d8-74df-be7e-95e1ce37eb3a
Final url
https://luntle-thrum.shop/
Status
200
Redirected
https-only
Redirects
[
    {
        "to": "https://luntle-thrum.shop/",
        "from": "http://luntle-thrum.shop/",
        "status": 307
    }
]
Ip
34.8.77.192
Ptr
192.77.8.34.bc.googleusercontent.com
Contacted IP addresses
[
    "34.8.77.192"
]
Asns
[
    "396982"
]
Countries
[
    "US"
]
Document hash
6c5d74593398868b7285edba64f53c5db909a6fd2cf4052b5a617609d3b62b5d
Tls
{
    "san": [
        "luntle-thrum.shop"
    ],
    "cipher": "AES_128_GCM",
    "issuer": "WR3",
    "subject": "luntle-thrum.shop",
    "protocol": "TLS 1.3",
    "valid_to": "2027-01-13T04:30:32Z",
    "valid_from": "2026-10-15T03:35:59Z"
}
Domain age days
16
Apex age days
16
Tls age days
16
Tls valid days
90
Requests
2
Provider verdicts
{
    "engines": {
        "tags": [
            "urlscan-ml",
            "urlscan-ml-60c5e22"
        ],
        "score": 91,
        "malicious": true
    },
    "overall": {
        "score": 0,
        "malicious": false
    }
}
HTTP headers
{
    "server": "nginx",
    "content-type": "text/html; charset=utf-8"
}
Separate monitor record · date not recorded

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

record_source
domain_monitor.urlscan
uuid
01a14867-2a0d-7318-a7e6-d029772701da
score
null
malicious
null
result_at
null
enriched_at
null
source_timestamps
{"urlscan_result_at":null,"urlscan_enriched_at":null}
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

OTX

3 community references

Open report

Cloudflare Radar

provider verdict: clean

Open report
Cloudflare RadarOriginal source recordObserved: 3 fields

Observed: · Retrieved:

Report ID

7a9a0642-b07b-4c3c-a5fb-2d92d45c1b71

Final URL

https://luntle-thrum.shop/

Document hash

b411bac46e385b926d10902e9bc275b9e5da962e50ca7e12e391acd482ee15b9
Original source fields · JSON
Uuid
7a9a0642-b07b-4c3c-a5fb-2d92d45c1b71
Final url
https://luntle-thrum.shop/
Document hash
b411bac46e385b926d10902e9bc275b9e5da962e50ca7e12e391acd482ee15b9

Google Safe Browsing

No threat flag

Open report

PhishDestroy DOM

0 / 100 · heuristic score · 0 brand references · 0 classifications

Open report
Separate monitor score · 0 / 100 · 2026-10-31T11:20:09Z

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
0
analyzed_at
2026-10-31T11:20:09Z
source_timestamp
2026-10-31 12:20:09
timestamp_basis
Europe/Berlin, as used by the existing report; source timestamps are retained verbatim

PhishDestroy narrative

Narrative generation metadata

Open report
Title, description and generation record

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

ai_title
luntle-thrum.shop — Polish password prompt page
ai_description
PhishDestroy records luntle-thrum.shop as a Polish-language page asking visitors to enter a password and confirm it.
ai_summary
The captured page on luntle-thrum.shop presents a single centered prompt in Polish: a masked heading reading "H***a", a text field with the placeholder "Proszę podać hasło" (please enter the password), and a brown button labeled "potwierdzić" (confirm). The HTML title "ostrzeżenie - H***a" (warning) frames the page as a warning screen, yet the visible content offers no explanation of what is being warned about — only the password request. The layout is otherwise empty, with no branding, links, or supporting text visible in the capture. The stored VirusTotal domain result reports 17 detections out of 92 engines. CRDF reported "malicious"; DNS8 reported "suspicious".
ai_generated_by
threat-v6-mimo
ai_generated_at
2026-10-31 12:16:23
revision
781b84b7cf319064cfb3784868efdd5124f9c337bbe574df4056cbb6a41b6d76
mode
reviewed
interpretation
Selected public package; text generation time is separate from source observation dates.

Results reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.

Collected source details

Stored page, network and scanner observations, grouped by source and observation time.

Every stored field, with its source and date
Website checksOriginal source recordRetrieved: 21 fields

Mail configuration

SPF lookups
0

CAA records

Domain
luntle-thrum.shop

Protective DNS results

Resolvers checked
12
Blocked by
  • CloudFlare Family
Blocking resolvers
1

Page title and metadata

Page title
500 Internal Server Error
Indexing directives
noindex, nofollow

Trackers

Requests
6
Observed services
  • Name
    Google Static
    Company
    Google
    Country
    US
    Category
    Hosting
    Requests
    2

Forms and mixed content

Third-party scripts
0

HTTP response

Reachable
Yes
HTTP status
200
Request timings, ms
DNS
791
TLS
32
Waiting
331
Connection
7
Download
0
Response time, ms
1161

TLS connection

ALPN
h2
Cipher
TLS_AES_256_GCM_SHA384
Protocol
TLSv1.3
Supported versions
  • TLSv1.2
  • TLSv1.3
Certificate authorized
Yes
Forward secrecy
Yes

Ports

Open ports
  • 80

Carbon estimate

Bytes
219
CO₂, grams
0
Cleaner than, %
95

DNS servers

Nameservers
  • IP address
    211.99.99.33
    Host
    ns2.dnsip.com
  • IP address
    1.193.216.199
    Host
    ns1.dnsip.com
DNS zone
luntle-thrum.shop

Cookies

Cookies
  • Name
    _baffid_vid
  • Name
    _baffid_cvid
  • Name
    _baffid_vs
  • Name
    utm_source
  • Name
    utm_medium
  • Name
    order_utm_history
  • Name
    landing_page
  • Name
    _baffid_ka
  • Name
    first_http_referer
  • Name
    first_visit_time
  • Name
    oemsaas_firewall
  • Name
    PHPSESSID
    Session cookie
    Yes

Location

IP address
34.8.77.192
ASN
396982
Organization
Google LLC
City
Kansas City
Country
US

TLS certificate

Issuer
Google Trust Services / WR3
Subject
luntle-thrum.shop

DNS records

A
  • 34.8.77.192
NS
  • ns1.dnsip.com
  • ns2.dnsip.com
SOA
Primary nameserver
ns1.dnsip.com
Hostmaster
dnsadmin.dnsip.com
Serial
1792036724
Refresh, seconds
3600
Retry, seconds
300
Expiry, seconds
1209600
Minimum TTL, seconds
1800

DNSSEC

DS record
No
RRSIG
No
DNSKEY
No

HSTS

Observation
Site does not serve any HSTS headers.

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
No
Cross-Origin-Opener-Policy
No
Cross-Origin-Embedder-Policy
No
Cross-Origin-Resource-Policy
No

IP lookup

IP address
34.8.77.192
IP version
4

Redirects

Redirect chain
  • https://luntle-thrum.shop

HTTP headers

Response headers
Server
nginx
Content-type
text/html; charset=utf-8
Original source fields · JSON
Mail configuration
{
    "spf_lookups": 0
}
Caa records
{
    "domain": "luntle-thrum.shop"
}
Protective DNS results
{
    "resolvers": 12,
    "blocked_by": [
        "CloudFlare Family"
    ],
    "blocked_count": 1
}
Page title and metadata
{
    "title": "500 Internal Server Error",
    "robots": "noindex, nofollow"
}
Trackers
{
    "requests": 6,
    "trackers": [
        {
            "name": "Google Static",
            "company": "Google",
            "country": "US",
            "category": "Hosting",
            "requests": 2
        }
    ]
}
Forms and mixed content
{
    "third_party_scripts": 0
}
Status
{
    "up": true,
    "code": 200,
    "timings": {
        "dns": 791,
        "tls": 32,
        "wait": 331,
        "connect": 7,
        "download": 0
    },
    "response_ms": 1161
}
TLS connection
{
    "alpn": "h2",
    "cipher": "TLS_AES_256_GCM_SHA384",
    "protocol": "TLSv1.3",
    "versions": [
        "TLSv1.2",
        "TLSv1.3"
    ],
    "authorized": true,
    "forward_secrecy": true
}
Ports
{
    "open": [
        80
    ]
}
Carbon
{
    "bytes": 219,
    "co2_grams": 0,
    "cleaner_than": 95
}
Dns server
{
    "ns": [
        {
            "ip": "211.99.99.33",
            "host": "ns2.dnsip.com"
        },
        {
            "ip": "1.193.216.199",
            "host": "ns1.dnsip.com"
        }
    ],
    "zone": "luntle-thrum.shop"
}
Cookies
{
    "cookies": [
        {
            "name": "_baffid_vid"
        },
        {
            "name": "_baffid_cvid"
        },
        {
            "name": "_baffid_vs"
        },
        {
            "name": "utm_source"
        },
        {
            "name": "utm_medium"
        },
        {
            "name": "order_utm_history"
        },
        {
            "name": "landing_page"
        },
        {
            "name": "_baffid_ka"
        },
        {
            "name": "first_http_referer"
        },
        {
            "name": "first_visit_time"
        },
        {
            "name": "oemsaas_firewall"
        },
        {
            "name": "PHPSESSID",
            "session": true
        }
    ]
}
Location
{
    "ip": "34.8.77.192",
    "asn": "396982",
    "org": "Google LLC",
    "city": "Kansas City",
    "country": "US"
}
Ssl
{
    "issuer": "Google Trust Services / WR3",
    "subject": "luntle-thrum.shop"
}
DNS records
{
    "A": [
        "34.8.77.192"
    ],
    "NS": [
        "ns1.dnsip.com",
        "ns2.dnsip.com"
    ],
    "SOA": "{\"nsname\": \"ns1.dnsip.com\", \"hostmaster\": \"dnsadmin.dnsip.com\", \"serial\": 1792036724, \"refresh\": 3600, \"retry\": 300, \"expire\": 1209600, \"minttl\": 1800}"
}
Dnssec
{
    "ds": false,
    "rrsig": false,
    "dnskey": false
}
Hsts
{
    "message": "Site does not serve any HSTS headers."
}
HTTP security policies
{
    "xFrameOptions": false,
    "referrerPolicy": false,
    "xXSSProtection": false,
    "permissionsPolicy": false,
    "xContentTypeOptions": false,
    "contentSecurityPolicy": false,
    "strictTransportPolicy": false,
    "crossOriginOpenerPolicy": false,
    "crossOriginEmbedderPolicy": false,
    "crossOriginResourcePolicy": false
}
Get ip
{
    "ip": "34.8.77.192",
    "family": 4
}
Redirects
{
    "chain": [
        "https://luntle-thrum.shop"
    ]
}
HTTP headers
{
    "headers": {
        "server": "nginx",
        "content-type": "text/html; charset=utf-8"
    }
}

Questions about luntle-thrum.shop

Is luntle-thrum.shop legit?

PhishDestroy records luntle-thrum.shop as a Polish-language page asking visitors to enter a password and confirm it.

Is luntle-thrum.shop safe to connect a wallet?

This report does not record which wallet requests luntle-thrum.shop 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 luntle-thrum.shop?

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

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

Checked, no match

Last checked

Stored Capture · 6 captures

Cloudflare Radar 1 / 6 Used in the analysis Source file SHA-256: 042d8610b63d9b69b8e6db0f095b6e9bef971bbe72080c93096502aad9d1bb70 SHA-256 of the prepared copy given to the model: 6da70f8b0952e799e605bd82d4a27da2d4d48ac98a3529da8036ada0044cd159
SourceCloudflare Radar
Recorded
StateStored capture
Final URLhttps://luntle-thrum.shop/
Position1 / 6
Open capture Source Report Wayback Download
All capture links and hashes (6)
Observed page title
ostrzeżenie - H***a
TLS Certificate
Issued by Google Trust Services / WR3 · stored validity ends in 73 days

Domain details

Domain
IP Reputation United States34.8.77.192 abuse score 0/100 0 reports checked Oct 31, 2026
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Registrar Spaceship US(US)
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for luntle-thrum.shop →
RegistrationCreated Oct 15, 2026 (17d · Very New!)
HTTP Status200
LLM Report Plain-text dossier structured for AI agents
Technical detailsProvenance & timestamps
First DetectedOct 31, 2026
DOM Analysisanalyzed Oct 31, 2026score 0/100
Submitted URLhttp://luntle-thrum.shop/
Favicon Hash
ICANN OVERSIGHT

Accreditation and RAA context

Registrar accreditation and DNS abuse obligations

For this gTLD, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.

Accreditation is a contract, not a safety certification.

RAA §3.18 establishes abuse-contact and handling requirements. This report can document stored outbound notices and later technical observations; it does not by itself establish receipt, investigation, remediation, or contractual non-compliance.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
United States34.8.77.192
Network ASN
AS396982
Organization
Google LLC
Observed location
United StatesKansas City, US
Server header
nginx

Nameservers 2

  • ns1.dnsip.com
  • ns2.dnsip.com

SOA

  • nsname: ns1.dnsip.com
  • hostmaster: dnsadmin.dnsip.com
  • serial: 1792036724
  • refresh: 3600
  • retry: 300
  • expire: 1209600
  • minttl: 1800

Location describes the IP network.

TLS certificate

Issuer
Google Trust Services / WR3
Valid from
2026-10-15 03:35:59
Valid until
2027-01-13 04:30:32
Hostname coverage
Stored certificate dates valid
Validity
Within stored validity dates
Collection source
PhishDestroy collector
Certificate fingerprintf0b2b7bfb3c8e61c366c4f4ab55c870356a8ef79483fb4e78285c1a209df96d0
Certificate names · 1 SAN
  • luntle-thrum.shop

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

viewdns.info · 34.8.77.192rapiddns.io

Latest Classified Outcome 2026-10-31 11:00:20 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: Resolved Registration: Unknown
Latest HTTP observation Live content Ordinary HTTP content served 90% 2026-10-31 11:00:20 UTC
RDAP registration
Observed timeline last reachable: 2026-10-31 11:24:12 UTC last content: 2026-10-31 11:00:20 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

17 / 92 security vendors flagged this domain
View on VT
Last analyzed Previous stored snapshot: 17 detections
alphaMountain.ai
BitDefender
CRDF
DNS8
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Gridinsoft
Kaspersky
LevelBlue
Lionic
PREBYTES
Seclookup
SOCRadar
Sophos
VIPRE

Archived Evidence

Wayback Machine Snapshot
View Archive
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of luntle-thrum.shop · checked Oct 31, 2026

92
Good
Performance
FCP
2.46 s
First Contentful Paint
LCP
2.46 s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
31 ms
Total Blocking Time
SI
3.96 s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
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://luntle-thrum.shop/
Final URL: https://luntle-thrum.shop/
ostrzeżenie - H***a
Response
HTTP 200
HTML body
371.2 KB
Compressed
70.3 KB
Links
0 internal · 0 external
Detected technologies
vuenginx
Selected response headers
Server: nginx
Content-Type: text/html; charset=utf-8
Content-Encoding: gzip
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 10
Alt-Svc
h3=":443"; ma=2592000
Content-Encoding
gzip
Content-Type
text/html; charset=utf-8
Date
Sat, 31 Oct 2026 10:53:07 GMT
execution-time
0.0334141254
Server
nginx
Transfer-Encoding
chunked
Vary
Accept-Encoding
Via
1.1 google
x-trace-id
3D6A3604-88C7-CABA-A195-CAB65A60CDAB

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: 2 SHA-256 hashes: 2 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-31 11:26 UTC.

Open this scan on URLScan 01a191b3-a9d8-74df-be7e-95e1ce37eb3a ↗

Stored observation history1

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

All retained availability observations4

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. dns_observationunknown
    Observation source
    dns_observation
    Cause
    probe_inconclusive
    Availability state
    unreachable
    Content state
    unknown
    DNS state
    resolved
    DNS response code
    NOERROR
    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-31 23:20:09.600237
    Evidence SHA-256
    fdac094cb4b92350d9f20b2c0fc69fdcaa33e7da7eb2d1063ea3f2bc257f29ef
    HTTP probe value as recorded
    0 · no HTTP response code recorded
    Evidence timestamp as recorded
    2026-10-31 23:20:09.600237
    Evidence reason
  2. current_http_probelive_content
    Observation source
    current_http_probe
    Cause
    content_served
    Availability state
    content_live
    Content state
    served_at_root
    DNS state
    resolved
    DNS response code
    NOERROR
    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:00:20.000000
    Evidence SHA-256
    241b6a67b7f560977980c46abc6cab1bd5a51e529ae5c4b520cc1f9ac701bac6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:00:20
    Evidence reason
    alive_content
  3. 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:00:20.000000
    Evidence SHA-256
    241b6a67b7f560977980c46abc6cab1bd5a51e529ae5c4b520cc1f9ac701bac6
    HTTP probe value as recorded
    200
    Evidence timestamp as recorded
    2026-10-31 12:00:20
    Evidence reason
    alive_content
  4. current_state_backfillunknown
    Observation source
    current_state_backfill
    Cause
    stale_current_evidence
    Availability state
    unknown
    Content state
    unknown
    DNS state
    stale
    Registration state
    unknown
    RDAP statuses
    []
    Recorded actor type
    unknown
    Monitor confidence
    0
    Provider action verified
    false
    Registrar mechanism verified
    false
    Linked to a report
    false
    Original source timestamp
    2026-10-31 11:49:09.563746
    Evidence SHA-256
    f3049ef8aa957a0c75d1f37b703ae6008630522768f5aca88bbd9915c9e1400b
    DNS evidence marked stale
    true
    HTTP evidence marked stale
    true

Threat Response Pipeline

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

Recorded events: 11. 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
    luntle-thrum.shop detected and queued for full analysis
Threat Intelligence ChecksSpamhaus DBL · URLScan.io Capture · URLScan Verdict · Cloudflare Radar Report · Web Archive · VirusTotal · OTX Community References · Forensic Evidence Collected · Technical Analysis Recorded Recorded: 9 of 9
  • Spamhaus DBL
    Spamhaus DBL recorded: phishing domain
  • URLScan.io Capture
    Stored URLScan report with capture artifacts
  • URLScan Verdict
    URLScan machine-learning engines classified the page as malicious · Score: 91
  • Cloudflare Radar Report
    A stored Cloudflare Radar report is available. The report link alone does not mean that the domain was classified as malicious, and it does not prove that every network field was captured.
  • Web Archive
    Preserved in the Wayback Machine: historical evidence archived
  • VirusTotal
    Detections recorded on VirusTotal: 17/92
  • OTX Community References
    Community publication references on AlienVault OTX: 3. References are not vendor verdicts and are excluded from the evidence score.
  • 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

5 entries
  1. URLScan

    Page captured

    View source
  2. AlienVault OTX

    3 community references

    View source
  3. Wayback Machine

    Page archived

    View source
  4. Added to PhishDestroy

    luntle-thrum.shop

    View source
  5. VirusTotal

    17/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

Check for cloaking

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

luntle-thrum.shop

Evidence & External Reports

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

Were You Affected by This Site?

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

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 luntle-thrum.shop)
  • 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.

The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.

A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.

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/luntle-thrum.shop"
  title="PhishDestroy threat report for luntle-thrum.shop"
  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>