The domain aprolo.shop returned an HTTP 502 response on 2026-10-03, indicating a server-side error. Google Safe Browsing flagged the site on the same date for social engineering.
Recorded Evidence
Google Safe Browsing detected social engineering on 2026-10-03. VirusTotal reported 2 detections out of 91 scanners on 2026-10-02. OTX listed the domain in 2 pulses on 2026-10-03. The domain was registered on 2026-03-16 through Spaceship, Inc.
Interpretation
Google’s social engineering flag indicates potential deceptive practices detected at the time of review. The HTTP 502 response documents a server failure on the same day, which may affect access to any content. The PhishDestroy internal listing also flagged the domain.
Recommended Actions
Review the Google Safe Browsing report for aprolo.shop to understand the social engineering flag. Compare VirusTotal detections and OTX pulse listings for the same domain to assess consistency. Do not rely on the domain’s availability or content based solely on the HTTP 502 response.
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.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-13 10:00:13 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:00:13 UTClast content: 2026-10-13 10:00:13 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.
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-10-03 08:30:49 UTC
VirusTotal scanner detections updated from 1 to 2. Added scanner alerts: SOCRadar.
VirusTotal Detections Update2026-10-03 06:03:36 UTC
VirusTotal scanner detections updated from 0 to 1. Added scanner alerts: CyRadar.
Status Check2026-10-02 19:24:37 UTC
Telemetry event observed.
Threat First Observed2026-10-02 19:24:04 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 188.244.119.61.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
13 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.
Web Archive
Preserved in ウェイバック・マシン — historical evidence archived
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)
