On 2026-10-01, track.mail.bc372.com returned an HTTP 502 status during an observation recorded for that domain. The same hostname was first observed on 2026-08-26, according to the recorded timeline.
Recorded Evidence
The PhishDestroy internal listing records track.mail.bc372.com as listed, with that listing checked on 2026-10-01. VirusTotal recorded 4 detections across 90 scanners for this domain on 2026-09-06. The HTTP check on 2026-10-01 returned status 502, and the first observation of the domain is dated 2026-08-26.
Interpretation
The PhishDestroy listing and the HTTP check share the 2026-10-01 date, so they describe the same review window, while the VirusTotal result from 2026-09-06 predates both. Because the first observation on 2026-08-26 is earlier than every other dated record, the timeline shows the domain was seen before the later checks. These dated records allow comparison of when each source observed the domain, without establishing what the domain does.
Recommended Actions
Retain the dated records for track.mail.bc372.com, including the PhishDestroy listing and the VirusTotal result, so later observations can be compared against them. When reviewing track.mail.bc372.com, avoid submitting passwords, payment details, or other sensitive information until the review is complete. Compare any subsequent HTTP check and listing status with the 2026-10-01 and 2026-09-06 records rather than relying on a single snapshot.
Detection-evasion analysis
Cloaking and traffic-distribution check
Not yet scannedNo 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
Last cloaking scan
Scanner note:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='track.mail.bc372.com', port=80): Max retries exceeded with url: / (Caused by NewConnection
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
What we count
Elapsed time from the first stored abuse report to the first observation that the content was unavailable. This does not establish the cause.
What each report contains
Stored outgoing-report records may reference evidence available at the time, such as vendor verdicts, registration data, hosting details, classifications, or screenshots. This page does not infer the exact payload delivered, receipt, acknowledgement, or action by a recipient.
Technical detailsProvenance & timestamps
First DetectedAug 26, 2026
Favicon Hash
Page Title
Georgina's Cottage
TLS Certificate
Hostname coverage not recorded·
Issued by WE1
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
CloudFlare, Inc.
Observed location
Toronto, CA
Server header
cloudflare
Edge-IP reputation is not attributed to this domain.
Nameservers 1
patrick.ns.cloudflare.com
Location describes the IP network.
TLS certificate
Issuer
WE1
Hostname coverage
Hostname coverage not recorded
Collection source
PhishDestroy collector
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-13 01:14:19 UTC
RDAP registrationUnknown
Observed timelinelast reachable: 2026-08-26 17:28:27 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-08-26 17:28:27 UTC → 2026-09-30 16:14:55 UTC · 838.77hmidpoint estimate ≈ 2026-09-13 04:51:41 UTC · precision very low · basis bounded
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 First positive detection Previous stored snapshot: 1 detection
alphaMountain.ai
CRDF
Forcepoint ThreatSeeker
SOCRadar
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.
Domain Status Transition2026-09-08 10:00:28 UTC
Domain state transitioned from alive to dead.
VirusTotal Detections Update2026-09-04 17:25:44 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: SOCRadar.
Threat First Observed2026-09-04 12:03:10 UTC
Domain ingestion complete. Initial state is marked as alive.
Threat Response Pipeline
Discovery
Analysis
Monitoring
10 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
track.mail.bc372.com detected and queued for full analysis
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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 8, 2026
Time to First Unavailability
305 hours elapsed from detection to the first unavailable observation.
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+
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.
3 evidence signal groups linked0 reports recordedContent unavailable
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.
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 →
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
Related Infrastructure & Reports
Stored relationships are grouped by the exact matching attribute. A shared provider or registrar alone does not prove common ownership.
Direct link Shares a registration or an identical phishing kit.
Supporting signal Shares infrastructure or a target brand; not proof of one operator.
Discovery only Listed for navigation; no shared attribute with this host.
Infrastructure map · track.mail.bc372.com
Each lane is one reason a domain is linked to this host. Node size marks VirusTotal detections and dashed nodes are already offline. The full lists follow below.
Content matches5
Same favicon hash or the same page title as this host.
(SG)
