Skip to security report
Analytics Dashboard
Domain security report
bhuroom.shop favicon

bhuroom.shop

Threat verdict
HighDomain Appeal
Assessment sources

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

Availability Unverified No conclusive current response is stored
Risk signals
VirusTotal detections: 6/92
OTX: 2 refs Oct 16, 2026
API
Resolved IP
212.52.28.18
1 sources
The capture source is temporarily unavailable.
Source
Primary capture
Collected · UTC
Open capture
This domain has been flagged as malicious
Security engines reporting a detection: 6. Exercise extreme caution — do not enter credentials or personal information.
Additional indicators at a glance
VirusTotal
VirusTotal
6 det.
OTX references
2 community refs
URLScan
URLScan
Report ↗
PhishDestroy
DestroyList
Listed

Source evidence

6 · 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

6 / 92

Report
Interpretation & limits

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

OTX

2 community references

Report
Interpretation & limits

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

URLScan capture

stored report

Observation time not recorded
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.

Public blocklists

0 external matches

Details
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
6/92
OTX
2 community refs
URLScan
Stored capture

Stored narrative · generated . Provider checks below retain their own observation dates.

Assessment

The domain bhuroom.shop was first observed on 2026-10-16, with a recorded entry in the publisher-owned PhishDestroy internal listing on the same date. VirusTotal also contains a relevant scan with multiple detections, providing additional context for security assessment.

Read the full analysis3

Recorded Evidence

VirusTotal checked bhuroom.shop on 2026-10-11, recording 6 detections out of 92 scanners. OTX references the domain with two pulses as of 2026-10-16. PhishDestroy internal listing documents the domain on 2026-10-16, marking its presence in their catalogue.

Interpretation

PhishDestroy contains a listing for bhuroom.shop, which records its observation and inclusion in a publisher-managed catalogue. VirusTotal measures the domain against a range of scanners and records detection counts, offering a quantitative perspective on its scan results. OTX provides intelligence entries called pulses, which serve as references for external security context. The evidence spans multiple sources and dates, allowing for comparison across different security records.

Recommended Actions

Preserve the documented records from PhishDestroy, VirusTotal, and OTX for bhuroom.shop in any ongoing review. Compare future scans and intelligence entries against these source records to monitor changes or new observations. Reference the catalogue and detection counts to inform further technical analysis and security checks.

Data coverage & collection12 · datasets with records / 19 · 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
6 / 92 · engine detections
URLScan analysis
Capture retained; no provider verdictCollection time not recorded
Google Safe Browsing
Checked; no threat flag recorded
OTX publications
2 · community references
External blocklists
0 · external matches
Cloudflare Radar
Report link retainedCollection time not recorded
Network & DNS
212.52.28.18 · 0 · nameserversCollection time not recorded
Page captures
1 · retained captures
HTML archives
1 · retained responses
Site configuration files
robots.txt · sitemap.xml · security.txt
Availability history
1 · stored state changes
Source observation history
1 · stored source events
Not recorded in this report 19

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

  • URLQuery
  • PhishStats
  • DNS security filters
  • Gridinsoft
  • Scamadviser
  • Spamhaus DBL
  • Domain registration
  • TLS certificate
  • Page analysis
  • Observed indicators
  • Detection & evasion
  • PageSpeed performance
  • Response records
  • Recorded subdomains
  • Lookalike relationships
  • Community reports
  • Chainabuse records
  • IP reputation
  • Wayback archive
Download the dated observations and supporting metadata.
Blocklist records0 · external source matches

Public Blocklist Status

Domain, network & archive212.52.28.18 · DNS, TLS and retained responses

Domain details

Domain
OTX tags 2026-10all-domainsblocklistcryptodomainsdrainerfraudmonthlyphishdestroyphishingscam
Technical detailsProvenance & timestamps
First DetectedOct 16, 2026
Submitted URLhttp://bhuroom.shop/

Network & certificates

Stored technical evidence

Network & DNS

Resolved IP
212.52.28.18

Location describes the IP network.

viewdns.info · 212.52.28.18rapiddns.io

Latest Classified Outcome 2026-10-16 00:03:56 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

6 / 92 security vendors flagged this domain
View on VT
Last analyzed First positive detection Previous stored snapshot: 6 detections
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
Gridinsoft
LevelBlue
Netcraft
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 404
Requested URL: http://bhuroom.shop/
Final URL: https://bhuroom.shop/
Response
HTTP 404
HTML body
21 B
Compressed
41 B
Links
0 internal · 0 external
Selected response headers
Content-Encoding: gzip
Content-Type: text/plain;charset=UTF-8
Security headers present
X-Frame-OptionsX-Content-Type-OptionsX-XSS-ProtectionReferrer-Policy
HSTS: not observed DNSSEC: not observed WAF / firewall: not observed Cloaking flag: not observed
Saved response-header values · 11
Alt-Svc
h3=":443"; ma=2592000
Content-Encoding
gzip
Content-Type
text/plain;charset=UTF-8
Date
Fri, 16 Oct 2026 00:00:08 GMT
Referrer-Policy
strict-origin-when-cross-origin
Transfer-Encoding
chunked
Vary
Accept-Encoding
Via
1.1 Caddy
X-Content-Type-Options
nosniff
X-Frame-Options
SAMEORIGIN
X-XSS-Protection
1; mode=block

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

Unverified (legacy)
/robots.txt
HTTP response
301
Observed at
2026-10-16 00:00:09 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Sitemap

Unverified (legacy)
/sitemap.xml
HTTP response
301
Observed at
2026-10-16 00:00:09 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

security.txt

Unverified (legacy)
/.well-known/security.txt
HTTP response
301
Observed at
2026-10-16 00:00:09 UTC
Source
legacy scan archive

A legacy response is stored, but it does not establish whether the file exists.

Detection & evasion checksStored 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 00:00:09 UTC
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Timeline & responseCollection 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 00:00:05 UTC
    Source: PhishDestroy monitoring
    Event details
    Domain ingestion complete. Initial state is marked as unknown pointing to IP 212.52.28.18.
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
bhuroom.shop detected and queued for full analysis
Oct 16, 2026
URLScan.io Capture
Stored URLScan report with capture artifacts
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
6/92 recorded on VirusTotal
Oct 16, 2026
OTX Community References
2 community publication references on AlienVault OTX. References are not vendor verdicts and are excluded from the evidence score.
Oct 16, 2026
Forensic Evidence Collected
Stored evidence from URLScan.io, stored screenshot
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 infrastructureShared hosting, registrar records and related domains
Evidence & investigation toolsOriginal reports, independent checks and evidence links

Evidence & External Reports

Security Analysis
URLScan Stored capture VirusTotal 6 det. ChainPatrol URLQuery SSL Labs CF Radar Open report OTX 2 refs 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 & reportingRecovery steps, reporting contacts and complaint drafts

Were You Affected by This Site?

4 evidence signal groups linked 0 reports recorded Unverified
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.

Europol
Find the official reporting channel for your EU country
National police directory
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

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
Embed this reportA 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/bhuroom.shop"
  title="PhishDestroy threat report for bhuroom.shop"
  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>