Security engines reporting a detection: 15. Public blocklists reporting a match: 2. Exercise extreme caution — do not enter credentials or personal information.
On 2026-10-03, ads-runtime-0388684858-corp.com returned an HTTP 502 error, documenting a server-side response at that time. The domain was also listed on two external blocklists, which were MetaMask and SEAL.
Recorded Evidence
Google Safe Browsing flagged the domain for social engineering threats on 2026-09-13. On that same date, VirusTotal recorded 15 detections out of 89 scanners for ads-runtime-0388684858-corp.com. The domain appeared in two OTX pulses as of 2026-09-13. Internal listing on Phishdestroy was present, and the domain was first observed on 2026-08-16.
Interpretation
These records show that multiple monitoring sources, including Google Safe Browsing, VirusTotal, and OTX, have noted ads-runtime-0388684858-corp.com for potential security concerns. The HTTP 502 response documents only the technical state of the server on a specific date, while the blocklist and detection records reflect external attention from several security platforms.
Recommended Actions
For further review, retain the blocklist entries, Google Safe Browsing flag, and VirusTotal scan results for ads-runtime-0388684858-corp.com. Preserve OTX pulse references and the internal Phishdestroy listing for comparison with future records and to support ongoing monitoring.
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='ads-runtime-0388684858-corp.com', port=80): Max retries exceeded with url: / (Caused by Ne
Live TDS fingerprint check
Seven Keitaro fingerprints plus a crawler-versus-browser comparison, run from the PhishDestroy scanner when this panel is open.
Waiting
Domain details
Domain
Google Safe BrowsingFlaggedSocial engineeringchecked Sep 13, 2026
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 16, 2026
Network & certificates
Stored technical evidence
Network & DNS
Nameservers 1
jamie.ns.cloudflare.com
Location describes the IP network.
Latest Classified Outcome 2026-10-10 20:20:48 UTC
Primary outcomeDNS inactivereason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observationUnknownProbe Inconclusive20%2026-10-11 01:00:18 UTC
RDAP registrationUnknown
Observed timelinecurrent episode first observed: 2026-09-30 16:14:55 UTCfirst terminal observation: 2026-09-30 16:14:55 UTC
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: 14 detections
alphaMountain.ai
BitDefender
CRDF
ESET
Forcepoint ThreatSeeker
Fortinet
G-Data
Google Safe Browsing
Gridinsoft
LevelBlue
Lionic
SOCRadar
Sophos
VIPRE
Webroot
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.
VirusTotal Detections Update2026-09-13 02:50:27 UTC
VirusTotal scanner detections updated from 14 to 15. Added scanner alerts: LevelBlue.
Domain Status Transition2026-09-12 23:04:51 UTC
Domain state transitioned from alive to dead.
Status Check2026-09-12 19:00:07 UTC
Telemetry event observed.
Threat Response Pipeline
Discovery
Analysis
Monitoring
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
Threat Ingested
ads-runtime-0388684858-corp.com detected and queued for full analysis
Aug 16, 2026
Spamhaus DBL
Spamhaus DBL recorded DBL_PHISH
Sep 13, 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.
The latest stored checks indicate that the reported content is unavailable; this does not establish who or what caused the change.
Sep 13, 2026
Time to First Unavailability
668 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.
2 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 →
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.
(HK)
