Stored registration data identifies NICENIC INTERNATIONAL GROUP CO., LIMITED (IANA 3765) as the registrar. PhishDestroy maintains separate NiceNIC abuse-report research; registrar association is contextual and is not an independent detection for this domain.
On 2026-10-01, an HTTP check of pierwlokatum.net returned status code 200, a recorded response that does not by itself establish present availability or site content. The domain was first observed on 2026-09-16, and a PhishDestroy internal listing is recorded as true.
Recorded Evidence
The HTTP check on 2026-10-01 returned status 200, while the first observation of pierwlokatum.net is dated 2026-09-16. VirusTotal, checked on 2026-09-29, reported 13 detections across 91 scanners. OTX, checked on 2026-09-18, recorded 4 pulses. The domain was registered on 2026-02-27 with registrar NICENIC INTERNATIONAL GROUP CO., LIMITED, and an SSL scan on 2026-09-17 identified the issuer as Let's Encrypt / YE1. A PageSpeed check on 2026-09-16 returned a performance score of 56.
Interpretation
The PhishDestroy internal listing and the OTX pulse count are separate catalogue records, each reflecting its own collection context rather than a shared measurement. The VirusTotal detection ratio and the HTTP status describe different kinds of observation, so they should be read independently instead of combined into a single trend. The recorded dates span from 2026-09-16 to 2026-10-01, which allows a reader to see the sequence of checks without treating any gap as evidence of change.
Recommended Actions
Preserve the PhishDestroy listing record and the OTX pulse entry for pierwlokatum.net as separate source artifacts, since each carries its own collection context. Compare the VirusTotal detection count against the OTX pulse record in future reviews, keeping their distinct measurement scopes in mind. Retain the HTTP response record alongside the PageSpeed score so later checks can be compared against the same source types.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: HTTP access restricted50% confidence
Attributionmechanism: Access Restrictionsource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Active
Latest HTTP observationReachable but protectedHTTP access restrictedAccess Restriction50%2026-10-12 02:39:33 UTC
RDAP registration有效NICENIC INTERNATIONAL GROUP CO., LIMITED · IANA 3765RDAP HTTP 200source: Rdap Status CollectorclientDeleteProhibitedclientTransferProhibitedexpires 2027-02-27 18:51:39 UTCchecked 2026-09-17 04:42:08 UTC
Observed timelinelast reachable: 2026-10-12 02:39:33 UTClast content: 2026-10-07 11:04:30 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.
Google PageSpeed Insights — mobile performance audit of pierwlokatum.net· checked Sep 16, 2026
56
Needs Work
Performance
FCP
9.16s
First Contentful Paint
LCP
9.61s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
53ms
Total Blocking Time
SI
9.16s
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.
VirusTotal Detections Update2026-09-16 22:06:28 UTC
VirusTotal scanner detections updated from 15 to 14. Resolved alerts: Seclookup.
Threat First Observed2026-09-16 19:00:21 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 91.236.116.210.
威胁响应 Pipeline
发现
Analysis
Monitoring
12 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Web Archive
Preserved in 互联网档案馆 — historical evidence archived
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.
(RU)
PhishDestroy Investigation
