Skip to security report
Analytics Dashboard
Domain security report
helplistings.blog favicon

helplistings.blog

Threat verdict
HighDomain Appeal
Assessment sources

Assessment based on the stored source evidence below. Review sources →

Availability Unverified Current reachability is unverified Observed · HTTP probe
Risk signals
VirusTotal detections: 3/92 Stored blocklist matches: 2 Young domain: 2 days old
Oct 16, 2026
API
Registrar
Hosting Concepts
Resolved IP
85.239.149.60
Registered
Oct 14, 2026
3 sources
The capture source is temporarily unavailable.
1 / 3
Source
Primary capture
Collected · UTC
Open capture
In this reportGet help
This domain has been flagged as malicious
Security engines reporting a detection: 3. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.

Additional indicators at a glance

VirusTotal
VirusTotal
3 det.
URLScan
URLScan
Report ↗
Age
2d Brand New!
PhishDestroy
DestroyList
Listed

Source evidence

7 · sources

These are dated observations, not a live safety check. No flag, a stored capture, or a completed analysis does not establish that a site is safe.

VirusTotal

3 / 92

Report
Interpretation & limits

Engine detections from this stored analysis. Vendors and collection times may differ from other sources.

Public blocklists

2 external matches

Details
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

URLQuery

Report stored; detailed verdict not recorded

Observation time not recorded
Report
Interpretation & limits

Alerts refer to the preserved scan. They do not describe the current state of the site.

OTX

no community references

Report
Interpretation & limits

Community publication references, not a vendor verdict or evidence of a common operator.

URLScan capture

stored report

View stored capture ↗
Report
Interpretation & limits

A preserved page image documents what the collector received; a capture is not a safety verdict.

CF Radar

Report stored; verdict not recorded

Observation time not recorded
Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Google Safe Browsing

Checked; no threat flag recorded

Report
Interpretation & limits

A result applies to the recorded source and observation time. Absence of a flag is not proof of safety.

Evidence Summary

High
VirusTotal
3/92
URLScan
Stored capture

AI-assisted analysis Stored narrative · generated . Provider checks below retain their own observation dates. This narrative is an interpretation of collected evidence, not an independent source verdict.

Assessment

helplistings.blog was recorded on 2026-10-16 with entries on the MetaMask and SEAL external blocklists, providing a dated reference for its listing status. The domain also achieved a PageSpeed performance score of 100 on the same date, reflecting its measured technical efficiency.

Recorded Evidence

On 2026-10-16, helplistings.blog appeared on both the MetaMask and SEAL external blocklists. VirusTotal checked the domain on 2026-10-15, documenting 3 detections out of 92 total scanners. PhishDestroy internally listed the domain, and PageSpeed measured a performance score of 100 on 2026-10-16. The domain was registered through Hosting Concepts B.V. d/b/a Registrar.eu on 2026-10-14.

Interpretation

PhishDestroy contains an internal listing for helplistings.blog, which documents its inclusion in a security intelligence record. VirusTotal provides a measurement of how many security engines detected the domain, offering a view of its evaluation by multiple scanners. The MetaMask and SEAL blocklist entries expand the scope of recorded observations, showing that multiple external sources referenced the domain within a short period.

Recommended Actions

For helplistings.blog, retain the records from PhishDestroy, VirusTotal, MetaMask, and SEAL for future comparison and review. Use the PageSpeed measurement as a technical reference point in subsequent assessments. Continue to monitor these sources for updated or additional entries relating to the domain.

Data coverage & collection

16 · datasets with records / 15 · not recorded

What this report contains, where it came from, and when it was collected. A retained record can be incomplete; collection status is separate from the threat assessment.

Recorded dataPartial recordUTC
VirusTotal
3 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
URLQuery
Stored source recordCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
0 · community references
External blocklists
2 · external matches
Cloudflare Radar
Report link retainedCollection time not recorded
Domain registration
Hosting Concepts B.V. d/b/a Registrar.euCollection time not recorded
Network & DNS
85.239.149.60 · 2 · nameserversCollection time not recorded
Page captures
3 · retained captures
HTML archives
1 · retained responses
Site configuration files
robots.txt · sitemap.xml · security.txt
PageSpeed performance
100/100 · mobile performance
Availability history
1 · stored state changes
Source observation history
1 · stored source events
IP reputation
Network-level observations
Not recorded in this report 15

These checks have no retained result. This does not mean they passed or that a scan is running.

  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Spamhaus DBL
  • TLS certificate
  • Page analysis
  • Observed indicators
  • Detection & evasion
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • Wayback archive
Download the dated observations and supporting metadata.

Blocklist records

2 · external source matches

Public Blocklist Status

Domain, network & archive

Hosting Concepts B.V. d/b/a Registrar.eu · 85.239.149.60 · DNS, TLS and retained responses

Domain details

Domain
IP Reputation abuse score 2/100 2 reports Open ProxyPort ScanHackingExploited Host checked Oct 16, 2026
Registrar Hosting Concepts NL(NL)
Abuse contactabuse@dedik.io, abuse@registrar.eu
ICANN RegistryICANN Lookup (RDAP) →
WHOIS LookupICANN RDAP for helplistings.blog →
RegistrationCreated Oct 14, 2026 (2d · Brand New!) — Expires Oct 14, 2027
Technical detailsProvenance & timestamps
First DetectedOct 16, 2026
Submitted URLhttp://helplistings.blog/
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.

Accreditation is a contract, not a safety seal. Verify ICANN fees Read RAA §3.18 PHISHDESTROY INVESTIGATIONICANN funding, contracts, and DNS abuse oversight
Accountability draft Nothing is sent automatically.

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
85.239.149.60
Nameservers 2
  • amos.ns.cloudflare.com
  • nina.ns.cloudflare.com

Location describes the IP network.

viewdns.info · 85.239.149.60rapiddns.io

Latest Classified Outcome 2026-10-16 19:31:00 UTC

Primary outcome Unknown reason: Stale Current Evidence 0% confidence
Attribution source: Current State Backfill
Evidence layers Availability: Unknown Content: Unknown DNS: Stale Registration: Unknown
RDAP registration Unknown
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.
Report This Domain Submit evidence & help protect others

VirusTotal Analysis

3 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection
alphaMountain.ai
Gridinsoft
SOCRadar
Site Performance Analysis

Google PageSpeed Insights — mobile performance audit of helplistings.blog · checked Oct 16, 2026

100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
0.76s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.75s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good 50-89 Needs Work 0-49 Poor
Stored Capture Evidence 1 snapshot

Timestamped response metadata retained by the local collection pipeline. Each value below belongs to the displayed archive time.

Archived HTTP response HTTP 200
Requested URL: http://helplistings.blog/
Vote
Community listing vote on CoinMarketCap.
Response
HTTP 200
HTML body
11.0 KB
Compressed
3.6 KB
Links
1 internal · 0 external
Selected response headers
Server: SimpleHTTP/0.6 Python/3.10.12
Content-Type: text/html; charset=utf-8
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Favicon fingerprint: 54e8edf66a7f7fad7d975470fa2ea7cc036757ba7897d05f8edf87f37cd47aab
Open Graph title: Vote
Open Graph description: Community listing vote on CoinMarketCap.
Twitter card: summary_large_image
Saved response-header values · 4
Content-Length
11274
Content-Type
text/html; charset=utf-8
Date
Fri, 16 Oct 2026 19:29:21 GMT
Server
SimpleHTTP/0.6 Python/3.10.12

Values retained by the collector; long values may be shortened during collection.

Archived
Crawler & disclosure files

Site configuration evidence

3 · file checks

Stored file checks, including unavailable and invalid responses. Retained contents and paths appear where available.

robots.txt

Not found
/robots.txt
HTTP response
404
Observed at
2026-10-16 19:29:23 UTC
Source
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

Sitemap

Not found
/sitemap.xml
HTTP response
404
Observed at
2026-10-16 19:29:23 UTC
Source
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

security.txt

Not found
/.well-known/security.txt
HTTP response
404
Observed at
2026-10-16 19:29:23 UTC
Source
legacy scan archive

The scanner received HTTP 404 or 410 for this file.

Detection & evasion checks

Stored browser and crawler observations

Detection-evasion analysis

Cloaking and traffic-distribution check

Not yet scanned No 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
Capture routing
Local archived 2026-10-16 19:29:23 UTC
Live TDS fingerprint check
Seven Keitaro fingerprints and a browser-versus-crawler comparison. A new scan starts only when you press the button.
On demand

No live-check result has been retained.

Timeline & response

Collection history, report status and investigation channels

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.
  1. Threat First Observed 2026-10-16 19:30:09 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 85.239.149.60.
Stored observation history2

Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.

  1. Availability monitor · Recorded state

    Unknown

    stale_current_evidence

  2. Availability monitor · First collection record

    Unknown

Threat Response Pipeline

Discovery
Analysis
Monitoring

7 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.

Threat Ingested
helplistings.blog detected and queued for full analysis
Oct 16, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
Oct 16, 2026
Cloudflare Radar Report
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.
VirusTotal
3/92 recorded on VirusTotal
Oct 16, 2026
Blocklist Detection
Found in 2 blocklists: MetaMask, SEAL
Oct 16, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, URLQuery, stored screenshot
Oct 16, 2026
DestroyList Published
Listed in the public PhishDestroy/DestroyList repository
Oct 16, 2026
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
urlscan.io Screenshot · DOM · HTTP

Capture the rendered page, requests and visible infrastructure.

VirusTotal Multi-engine verdicts

Compare the available engine results and retain the analysis timestamp.

Cloudflare Radar DNS · certificates · categories

Inspect a public scan and its recorded network and classification data.

AlienVault OTX Threat-intelligence pulses

Look for indicator references and related community intelligence.

Wayback Machine Historical evidence

Compare archived captures and preserve historical context.

crt.sh Certificate Transparency

Inspect certificate records and related hostnames.

DNS Security Filters Quad9 · AdGuard · CleanBrowsing

Compare security resolver responses and record observed blocking.

Web-Check Surface inspection

Inspect the public DNS, TLS, HTTP and technology surface.

02Abuse reports & follow-upRegistrar, hosting and security channels
  1. Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
  2. Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
  3. Send the report. Keep outgoing report records and recipient information when available.
  4. 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.

GoogleSafe Browsing GoogleWeb Risk MicrosoftSmartScreen VirusTotalURL analysis CloudflareRadar / abuse reporting YandexSafe Browsing URLScan.ioPublic scan ESETSample / URL submission BitdefenderURL submission NortonSafe Web SymantecSiteReview AviraURL reporting Avast / AVGURL reporting KasperskyOpenTIP Dr.WebOnline scanner NetcraftAbuse reporting PhishTankCommunity reporting APWG eCXPhishing intelligence PhishStatsPublic feed Phish.ReportHosting abuse SpamhausDomain reputation PolySwarmMulti-engine analysis CheckPhishURL scan QutteraMalware scan URLqueryBrowser analysis Criminal IPAsset intelligence CRDFThreat Center ScamadviserReputation check MyWOTCommunity reputation

Related infrastructure

Shared hosting, registrar records and related domains

Evidence & investigation tools

Original reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 3 det. ChainPatrol URLQuery Report stored SSL Labs CF Radar Open report WOT ScamAdviser Blacklist Checker URLVoid Sucuri SiteCheck MDN Observatory
OSINT & Intelligence
Web-Check Full scan SOCRadar Dark web report LeakIX Leak search Shodan Censys ThreatFox Hudson Rock Sign-in search IntelX crt.sh Certs WHOIS Wayback
DNS & Network
nslookup.io DNS bgp.tools ASN/Route
SEO & Domain
SpyFu Moz DA/PA Ahrefs Backlinks
Deep Analysis
Deep Analysis

Help & reporting

Recovery steps, reporting contacts and complaint drafts

Help & reporting

Were You Affected by This Site?

4 evidence signal groups linked 0 stored notification records Unverified

Listed domains receive at least one abuse report; this entry has no retained notification history.

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.

Immediate steps Find reporting contacts
Official reporting routes
PhishDestroy listing review Not a law-enforcement report
Domain Appeal
Request a review if you own this domain and believe the listing is incorrect
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 →
Report to Your Local Authorities

Select your country to get official cybercrime contacts, or create a complaint draft →.

97-country directory

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
After a phishing incident

Recommendations & Advice for Victims

Choose the steps that match what you shared. Keep a copy of this report alongside your own records.

What should I do immediately?

Urgent

Stop using the suspicious site. Open the real service through its official app or an address you already trust.

  • Change all passwords — email, exchange accounts, anything that shares the same password
  • Enable 2FA using an authenticator app (not SMS). Disable SMS-based recovery
  • Freeze cards if you entered banking details on the phishing site

What information should I collect for my report?

FBI guidelines

Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗

  • Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
  • Exact dates & times — of each transaction and first contact with scammer
  • Screenshots — scam website, chat messages, emails, wallet transactions, social media
  • All URLs & domains used by the scammer (including helplistings.blog)
  • Communications — emails, texts, phone numbers, usernames the scammer used

Even if you don't have all details — file a report anyway. Partial information still helps investigations.

Where should I report the scam?

  • FBI IC3 — Internet Crime Complaint Center (US federal reporting)
  • Europol — European cybercrime reporting (EU)
  • Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
  • Local police — creates an official record, even if they can't act immediately

A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.

How do phishing scams typically work?

  • Fake websites — pixel-perfect clones of legitimate sites with slightly altered domains
  • Pig butchering — trust built over weeks via Telegram/WhatsApp/dating apps, then money stolen
  • Recovery scams — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
  • AI-powered scams — deepfakes, automated phishing, and AI-generated sites making fraud harder to detect

How can I protect myself in the future?

  • Bookmark official sites — never click links from emails, DMs, or ads
  • Verify domains — check on PhishDestroy before interacting. Check HTTPS, spelling, domain age
  • "Too good to be true" = scam — guaranteed returns, celebrity endorsements, urgent deadlines

Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams

Check Any Domain

Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence

Scan Now

Report Phishing

Submit suspicious domains to our threat database — protect the community

Report

Live Threat Feed

Recent phishing reports and observed availability changes

Monitor

Stay Informed, Stay Safe

Monitor live threats or contest this listing if you believe it's a false positive

Live Threat Feed Appeal This Listing
Read the evidence in context

About This Report: helplistings.blog

Stored evidence snapshot. Source timestamps appear where available.

VirusTotal detections for helplistings.blog: 3 (2026-10-16 19:30:15 UTC).

Each source records a particular observation. A screenshot, an available website, or a result with no detections does not establish that a site is safe. Source results can change after they are collected.

submit an appeal or review the FAQ page.

Embed this report

A compact widget with a link to the evidence

HTML · IFRAME

Embed This Report

Share this threat intelligence on your website or blog

embed.html 
<iframe
  src="https://phishdestroy.io/embed/domain/helplistings.blog"
  title="PhishDestroy threat report for helplistings.blog"
  width="100%" height="320"
  loading="lazy"
  referrerpolicy="no-referrer"
  sandbox="allow-same-origin allow-popups allow-popups-to-escape-sandbox"
  style="border:0;border-radius:12px;max-width:100%"
></iframe>