VirusTotal
5 / 89
“Sign in - BAM®”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@hetzner.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.
bam.clearoute.dev returned HTTP 301 in the check recorded on 2026-10-01, indicating a redirect response at that time. The same domain appears on two named external blocklists, MetaMask and SEAL, according to the blocklist check dated 2026-10-01.
The HTTP check on 2026-10-01 recorded status 301 for bam.clearoute.dev. The external blocklist check on 2026-10-01 listed the domain on MetaMask and SEAL, a count of two. VirusTotal, checked on 2026-09-20, reported 5 detections across 89 scanners. The domain was first observed on 2026-09-06, the same date as the PageSpeed check, which returned a performance score of 61. The SSL scan on 2026-09-06 identified the issuer as Let's Encrypt / YR2. The IP address 5.161.181.176 is recorded in the United States under AS213230 Hetzner Online GmbH.
The MetaMask and SEAL listings and the VirusTotal detections are separate source observations, each with its own scope and measurement method, so they should be read individually rather than merged into a single conclusion. The HTTP 301 record describes one response on one date and does not establish what content, if any, the redirect leads to. The first-observed and SSL dates fall earlier than the blocklist and HTTP checks, but the records do not show what changed between them.
Preserve the MetaMask and SEAL blocklist records and the VirusTotal detection record for bam.clearoute.dev so they can be compared later. Separately retain the HTTP response record and the first-observed record, since each documents a different aspect of the domain's history. Anyone reviewing bam.clearoute.dev should consult the named sources directly and treat each dated record on its own terms.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
nginxScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://bam.clearoute.dev/; server=nginx
For the registrable domain clearoute.dev behind this subdomain, the registrar above operates under an ICANN accreditation agreement. The links below provide the official fee schedule and current DNS abuse compliance guidance.
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.
ns1.bam.clearoute.devns2.bam.clearoute.devLocation describes the IP network.
7ff6cdf590cf4a38402b733fabb6943a43d0708ae643b403b013bb21d08e15e7Saved 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 bam.clearoute.dev · checked Sep 6, 2026
5.161.181.176. 12 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-20260906-B63A29 Recipient: abuse@hetzner.com Policy Violations: Illegal Activities: Active phishing operation targeting victims Fraud & Deception: Impersonation of legitimate services Identity Theft: Collection of credentials under false pretenses Applicable Laws (Unknown): International Anti-Cybercrime Regulations Budapest Convention on Cybercrime Universal Fraud Prevention Laws Phishing activities violate international cybercrime conventions and Unknown's domestic fraud laws. Action Required: This evidence-backed report demonstrates clear violations requiring suspension per your policies. Continued hosting exposes your organization to regulatory scrutiny and potential legal liability.
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