VirusTotal
16 / 89
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@dynadot.com.
The latest stored availability evidence still shows the domain reachable; 1 month has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
| Detection System | Indicator | Verdict | Alert |
|---|---|---|---|
| DigiCert UltraDNS | helio-pulse.com |
malicious | Sinkholed |
| Quad9 DNS | helio-pulse.com |
malicious | Sinkholed |
| DNS4EU | helio-pulse.com |
malicious | Sinkholed |
| OpenDNS | helio-pulse.com |
phishing | Phishing Block |
| Cloudflare DNS | helio-pulse.com |
malicious | Sinkholed |
On 2026-10-02, an HTTP request to helio-pulse.com returned status code 200, according to the recorded HTTP check. The domain appears in the PhishDestroy internal listing, a publisher-owned catalogue, and VirusTotal recorded 16 detections across 89 scanners on 2026-09-18.
The HTTP check dated 2026-10-02 recorded status 200 for helio-pulse.com. OTX recorded 5 pulses on 2026-09-11. VirusTotal recorded 16 detections out of 89 scanners on 2026-09-18. The domain was first observed on 2026-09-05, the same date PageSpeed recorded a performance score of 100. The registration date is 2025-10-22 with registrar Dynadot Inc, and the SSL scan on 2026-09-06 named Google Trust Services / WE1 as issuer.
The HTTP, OTX, VirusTotal and PhishDestroy records describe separate observations made on different dates, so each should be read on its own terms rather than combined into a single judgment. The first-observed and PageSpeed dates coincide, but a shared calendar date does not establish simultaneous measurement or direct comparability. The PhishDestroy listing is a publisher-owned catalogue entry, and the VirusTotal figure reflects scanner output at one recorded moment.
Preserve the helio-pulse.com records from the HTTP check, OTX, VirusTotal and the PhishDestroy catalogue for later comparison. Compare the VirusTotal scanner output and the OTX pulse record in separate reviews, since they are distinct source records. Re-check the HTTP response and catalogue entry periodically to see whether later observations align with the recorded ones.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: alive_content: raw=ok; http=200; via=https_proxy; server=cloudflare
Edge-IP reputation is not attributed to this domain.
justin.ns.cloudflare.comraquel.ns.cloudflare.comLocation describes the IP network.
6de242fc82ee2c457630d41d3c410f02f72e06fa95816c8a7c1540d8a36f09a3Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of helio-pulse.com · checked Sep 5, 2026
188.114.97.3. 11 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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
PD-20260905-048F6A Recipient: abuse@dynadot.com Registrar: Dynadot LLC / Dynadot Inc (United States) Policy Violations: Acceptable Use forbids illegal content; Spam & Abuse Policy prohibits phishing, fraud, malware; Dynadot may disable DNS and suspend domains Applicable Laws: CFAA 18 U.S.C. §1030, Wire Fraud 18 U.S.C. §1343, CAN-SPAM Act
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive