19348.locker is a phishing page detected by PhishDestroy on 2026-02-26. Risk: critical (83/100). Status: Content unavailable. Hosting: CNSERVERS, US. VirusTotal: 11/93 engines flag it. Do not enter credentials or connect a wallet.
The domain 19348.locker is associated with a generic phishing operation, currently down or taken down, and has a critical threat score of 95/100. It has been flagged as malicious by 11 out of 95 security vendors, including notable names like BitDefender and ESET, and is listed on one public blocklist. Google Safe Browsing has not flagged this domain, indicating it may have been recently active without detection by that service.
Registrar information is not available, which suggests potential use of privacy protection or a lack of transparency. The domain was created on 2026-02-21 and was first detected on 2026-02-26. The hosting IP is 23.225.199.94, which should be flagged as an indicator of compromise. Block the domain at the perimeter and submit it to the registrar abuse desk for further investigation.
Questions about 19348.locker
Is 19348.locker legit?
No. PhishDestroy classifies 19348.locker as a phishing page (risk: critical, 83/100); it was first detected on 2026-02-26. VirusTotal: 11/93 engines flag it. Treat the site as unsafe.
Is 19348.locker safe to connect a wallet?
No. Do not connect a wallet, sign messages or approve tokens on 19348.locker. Phishing sites ask for approvals (approve, setApprovalForAll, Permit2) that let the operator move your assets, and a confirmed transaction cannot be reversed.
What should I do if I used 19348.locker?
Change every password you entered there and turn on two-factor authentication. If you connected a wallet or signed something, revoke the approvals and move the remaining funds to a new wallet; never share your seed phrase. Step-by-step help: emergency guide.
IP Reputationabuse score 0/1001 reportchecked Jun 15, 2026
RegistrationCreated Feb 21, 2026 (243d)
Time to First Unavailability28 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 Mar 24, 2026score 73/100
Observed page title
Welcome
TLS Certificate
Issued by R12
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
23.225.199.94
Network ASN
AS40065
Organization
CNSERVERS LLC
Observed location
Los Angeles, US
Server header
Caddy
Location describes the IP network.
TLS certificate
Issuer
R12
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-21 01:07:16 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-03-26 12:50:24 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-03-26 12:50:24 UTC → 2026-09-30 16:14:55 UTC · 4,515.41hmidpoint estimate ≈ 2026-06-28 14:32:39 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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='19348.locker', port=80): Max retries exceeded with url: / (Caused by NewConnectionError("S
19348.locker
Saved result
Unreachable
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
4 evidence signal groups linked0 stored notification recordsContent unavailable
Listed domains receive at least one abuse report; this entry has no retained notification history.
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
After a phishing incident
Recommendations & Advice for Victims
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
What should I do immediately?
Urgent
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Change all passwords — email, exchange accounts, anything that shares the same password
Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
Freeze cards if you entered banking details on the phishing site
What information should I collect for my report?
FBI guidelines
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Exact dates & times — of each transaction and first contact with scammer
Screenshots — scam website, chat messages, emails, wallet transactions, social media
All URLs & domains used by the scammer (including 19348.locker)
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)
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
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.
