The domain auspost.adqwi.com was observed in a recorded OpenPhish blocklist entry dated 2026-10-13, highlighting its inclusion in a curated security source. A high PageSpeed performance score was also measured for the domain, providing additional technical context for review.
Recorded Evidence
On 2026-10-13, auspost.adqwi.com appeared on the OpenPhish external blocklist. VirusTotal checked the domain on 2026-10-12, documenting 7 detections out of 92 total scanners. PhishDestroy internally listed the domain as of 2026-10-13. The PageSpeed performance score for auspost.adqwi.com was recorded as 100 on 2026-10-13.
Interpretation
The VirusTotal record contains a measurement of how multiple security engines detected the domain, offering a broad perspective on its evaluation by automated scanners. The OpenPhish listing documents that auspost.adqwi.com was included in an external blocklist, which is a curated source of security intelligence. These records provide a snapshot of how the domain was assessed by different security and performance tools within a close timeframe.
Recommended Actions
For auspost.adqwi.com, preserve the VirusTotal, OpenPhish, and PhishDestroy records for future comparison with subsequent scans and blocklist entries. Retain the PageSpeed performance score to monitor any changes in technical measurements over time.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Primary outcomeReachable but protectedreason: Captcha85% confidence
Attributionmechanism: Challengesource: Current Http Probe
Evidence layersAvailability: Reachable but protectedContent: UnknownDNS: ResolvedRegistration: Unknown
Latest HTTP observationReachable but protectedCaptchaChallenge85%2026-10-13 10:00:14 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-13 10:00:14 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: 7 detections
alphaMountain.ai
Emsisoft
Fortinet
カスペルスキー
ネットクラフト
SOCRadar
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of auspost.adqwi.com· checked Oct 13, 2026
100
Good
Performance
FCP
0.78s
First Contentful Paint
LCP
0.78s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.48s
Speed Index
Powered by Google PageSpeed Insights · Mobile strategy · Scores: 90-100 Good50-89 Needs Work0-49 Poor
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.
Threat First Observed2026-10-12 23:34:43 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 47.79.39.190.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
9 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.
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.
(HK)
