PhishDestroy first observed roblnhood.trade on Oct 13, 2026. Current evidence score: 100/100 (critical).
Positive findings are stored from 6 sources: VirusTotal, MetaMask, SEAL, Google Safe Browsing, Spamhaus DBL, and URLQuery. On Oct 13, 2026 at 18:48 UTC, VirusTotal recorded 16 detections among 92 engines: alphaMountain.ai, BitDefender, Chong Lua Dao, CRDF, CyRadar, ESET, Forcepoint ThreatSeeker, Fortinet, G-Data, Google Safe Browsing, Gridinsoft, Kaspersky, Lionic, Seclookup, Sophos, VIPRE; Google Safe Browsing flagged the domain: Social Engineering. MetaMask and SEAL listed the hostname in the separate external-blocklist snapshot on Oct 13, 2026 at 18:20 UTC. Spamhaus DBL: DBL_PHISH on Oct 13, 2026 at 18:30 UTC. URLQuery recorded 2 detections; no observation timestamp was retained. Additional recorded evidence: AlienVault OTX listed 3 community pulse references (not vendor detections) on Oct 13, 2026 at 18:48 UTC. URLScan captured the page on Oct 13, 2026 at 18:19 UTC.
The collector marked the hostname reachable on Oct 13, 2026 at 18:19 UTC, but did not retain the HTTP response code. Latest classified outcome: unknown; cause stale current evidence on Oct 13, 2026 at 16:18 UTC. Registration records for the domain list Global Domain Group LLC as the registrar and Mar 7, 2026 as the creation date. At collection time, the hostname resolved to 198.251.89.30 on AS53667 (FranTech Solutions). The recorded endpoint location is Luxembourg, LU. The evidence archive retains 3 visual captures from PhishDestroy and URLScan; the captures preserve the landing-page appearance. TLS metadata lists Let's Encrypt / YR1 as the certificate issuer with validity through Dec 6, 2026; checked Oct 13, 2026 at 19:02 UTC.
The record contains 6 positive source findings supporting the current phishing classification.
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.
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 Previous stored snapshot: 16 detections
alphaMountain.ai
BitDefender
Chong Lua Dao
CRDF
CyRadar
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
カスペルスキー
Lionic
Seclookup
ソフォス
VIPRE
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of roblnhood.trade· checked Oct 13, 2026
75
Needs Work
Performance
FCP
2.72s
First Contentful Paint
LCP
5.38s
Largest Contentful Paint
CLS
0.022
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
2.99s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-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 responseHTTP 200
Requested URL:http://roblnhood.trade/
Bot Verification
対応 HTTP 200
HTML body 1.7 KB
Compressed 791 B
Links 0 internal · 0 external
Selected response headers
Content-Type: text/html
Content-Encoding: gzip
Server: LiteSpeed
Cache-Control: no-cache,no-store,private
Security headers present
X-Frame-Options
HSTS: not observedDNSSEC: not observedWAF / firewall: not observedCloaking flag: not observed
Saved response-header values · 10
Cache-Control
no-cache,no-store,private
Connection
Keep-Alive
Content-Encoding
gzip
Content-Length
990
Content-Type
text/html
Date
Tue, 13 Oct 2026 18:17:48 GMT
Keep-Alive
timeout=5, max=100
Server
LiteSpeed
Vary
Accept-Encoding
X-Frame-Options
SAMEORIGIN
Values retained by the collector; long values may be shortened during collection.
Crawler & disclosure files
Site configuration evidence
1 recorded files
Files, paths and sitemap entries retained by the collector.
Sitemap
Reachable (legacy)/sitemap.xml
HTTP response
200
Observed at
2026-10-13 20:17:47 UTC
情報源
legacy scan archive
A legacy scan recorded a successful response. The file contents were not retained.
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.
Status Check2026-10-13 18:17:46 UTC
Telemetry event observed.
Threat First Observed2026-10-13 18:17:37 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 198.251.89.30.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
11 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.
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.
(US)
