As recorded on 2026-10-01, epicklocker.digital returned an HTTP status code of 502. The domain was first observed on 2026-08-24, and its registration date is listed as 2026-07-29.
Recorded Evidence
The PhishDestroy internal listing records epicklocker.digital as listed, and the domain was first observed on 2026-08-24. A PageSpeed check on 2026-08-24 returned a performance score of 73, while an SSL scan on the same date identified Let's Encrypt / YE2 as the certificate issuer. VirusTotal recorded 5 detections across 90 scanners on 2026-09-06. OTX recorded 4 pulses on 2026-08-28, and the registrar is PDR Ltd. d/b/a PublicDomainRegistry.com.
Interpretation
The HTTP 502 observation from 2026-10-01 and the first-observed date of 2026-08-24 come from different checks, so they describe separate moments rather than one continuous state. The PhishDestroy listing and the OTX pulse count were recorded on different dates, which means a reader should compare them as dated snapshots instead of treating them as a single synchronized result. The VirusTotal detection count of 5 out of 90 scanners on 2026-09-06 is also a dated snapshot, so it should be read alongside, not instead of, the other source records.
Recommended Actions
Anyone reviewing epicklocker.digital should retain the dated records from each named source so later observations can be compared against the 2026-08-24, 2026-08-28, 2026-09-06 and 2026-10-01 snapshots. When checking epicklocker.digital again, record the exact date and the source value rather than relying on memory. During review, avoid submitting passwords, payment details or other sensitive information to the domain until the recorded status is independently confirmed.
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='epicklocker.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionE
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 24, 2026
Submitted URLhttps://epicklocker.digital/
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.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:14:40 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-24 22:15:46 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-24 22:15:46 UTC → 2026-09-30 16:14:55 UTC · 881.99hmidpoint estimate ≈ 2026-09-12 07:15:20 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.
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
Forcepoint ThreatSeeker
Gridinsoft
SOCRadar
VIPRE
Site Performance Analysis
Google PageSpeed Insights — mobile performance audit of epicklocker.digital· checked Aug 24, 2026
73
Needs Work
Performance
FCP
4.45s
First Contentful Paint
LCP
4.52s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
59ms
Total Blocking Time
SI
4.45s
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-11 01:15:11 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-08-24 22:33:16 UTC
VirusTotal scanner detections updated from 0 to 5. Added scanner alerts: Forcepoint ThreatSeeker, Fortinet, Gridinsoft, SOCRadar, alphaMountain.ai.
Threat First Observed2026-08-24 06:24:12 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 158.94.211.169.
Threat Response Pipeline
Discovery
Analysis
Notifications
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
epicklocker.digital 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 11, 2026
Time to First Unavailability
426 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.
6 evidence signal groups linked1 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 · epicklocker.digital
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 matches4
Same favicon hash or the same page title as this host.
