Analysis of www.klorpagi.com shows a newly‑registered domain that is actively being used for phishing. The domain was created on July 12, 2026 and is registered through GoDaddy.com, LLC. It resolves to the single IPv4 address 185.158.133.1 and is served by the GoDaddy‑owned name servers ns71.domaincontrol.com and ns72.domaincontrol.com, suggesting a generic shared‑hosting environment. The site is currently listed on one public security blocklist and is blocked by the PhishDestroy filtering service, indicating that at least one anti‑phishing feed has identified malicious activity originating from this host.
VirusTotal reports that the domain was scanned by 91 security vendors, with none flagging it at the time of analysis; however, the absence of detections does not constitute evidence of legitimacy and should not be taken as a safety guarantee. No additional intelligence such as Safe Browsing, OTX citations, SSL certificate details, HTTP response codes, or page‑title metadata is available, leaving the exact phishing lure and target brand unknown. Given the confirmed malicious classification, defenders should immediately block www.klorpagi.com at network perimeters, update DNS‑based deny lists, and monitor for any related activity originating from the hosting IP.
Continuous re‑scanning with multiple detection engines is advised, as threat actors often modify payloads after initial deployment. Organizations should also consider adding the domain to internal threat intelligence feeds and correlating future alerts against the observed infrastructure to detect any potential resurgence or related campaigns.
Extracted from stored page analysis
Observed indicators
1 wallet · 0 Telegram
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
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='duplicate-disabled-377201.invalid', port=80): Max retries exceeded with url: / (Caused by
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
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 DetectedAug 4, 2026
DOM Analysisanalyzed Aug 4, 2026score 78/1002 brand signals
IoC Extractionscanned Aug 4, 20261 wallet · 0 Telegram IoC
Submitted URLhttps://www.klorpagi.com/
Favicon Hash
Case ID
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.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:30:59 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-09-15 22:18:17 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.
Technologies · 2 identified
H
HSTS
Security
HTTP Strict Transport Security (HSTS) informs browsers that the site should only be accessed using HTTPS.
Cloudflare is a web-infrastructure and website-security company, providing content-delivery-network services, DDoS mitigation, Internet security, and distributed domain-name-server services.
Google PageSpeed Insights — mobile performance audit of duplicate-disabled-377201.invalid· checked Aug 4, 2026
69
Needs Work
Performance
FCP
2.89s
First Contentful Paint
LCP
14.8s
Largest Contentful Paint
CLS
0.008
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
3.26s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
Forensic History & Detection Timeline
ThreatLifecycleTelemetry
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Domain Status Transition2026-09-25 01:31:10 UTC
Domain state transitioned from alive to dead.
Threat Response Pipeline
Discovery
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
duplicate-disabled-377201.invalid detected and queued for full analysis
A stored Cloudflare Radar report is available. The report link alone is not a malicious verdict and does not prove that every network field was captured.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 25, 2026
Time to First Unavailability
1245 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 →
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.
(US)
