helplist.blog was observed with a ScamSniffer blocklist entry on 2026-10-11, documenting an external detection for the domain. This entry provides a dated reference for its inclusion in a security intelligence source.
Recorded Evidence
ScamSniffer recorded helplist.blog in its blocklist on 2026-10-11. PhishDestroy internally listed the domain on the same date. The domain's registration with Hosting Concepts B.V. d/b/a Registrar.eu was noted on 2026-10-03, and an SSL certificate issued by Let's Encrypt / YR2 was scanned on 2026-10-11.
Interpretation
ScamSniffer provides a blocklist measurement for helplist.blog, recording its presence in an external security database. The PhishDestroy internal listing documents the domain in a separate context, offering another distinct reference. These observations allow for comparison between external and internal security records from the same date.
Recommended Actions
For helplist.blog, preserve the ScamSniffer blocklist entry and the PhishDestroy internal listing as reference points. Review future blocklist and internal listing records alongside these dated entries to monitor any changes in the domain's recorded status.
注册信息创建 2026年10月3日 (7d · Very New!)—Expires 2027年10月3日
HTTP 状态码200
技术详情Provenance & timestamps
首次发现2026年10月11日
DOM Analysisanalyzed 2026年10月11日score 83/1001 brand signal
Submitted URLhttp://helplist.blog/
Favicon Hash
案件 ID
ICANN OVERSIGHT
认证和 RAA 背景
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 observation未知Probe Inconclusive20%2026-10-11 08:33:01 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-11 08:33:01 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.
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.
Threat First Observed2026-10-11 08:33:01 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 93.152.205.16.
威胁响应 Pipeline
发现
Analysis
Monitoring
9 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
(NL)
