annulation-amazon.com was flagged by Google Safe Browsing for social engineering on 2026-10-06, highlighting a notable security-related observation. On the same date, the domain achieved a PageSpeed performance score of 100, indicating a technically responsive site at that time.
Recorded Evidence
Google Safe Browsing identified annulation-amazon.com for social engineering on 2026-10-06. Phishunt included the domain on its blocklist as of 2026-10-06. VirusTotal reported 19 detections out of 92 scanners on 2026-10-02. The registrar was Hosting Concepts B.V. d/b/a Registrar.eu, with the domain registered on 2025-08-31. Internal listing by Phishdestroy was also recorded.
Interpretation
The records from Google Safe Browsing, Phishunt, and VirusTotal provide several dated observations relevant to annulation-amazon.com. These sources document the domain’s appearance in security-related listings and detection services within a close timeframe, offering multiple perspectives for review.
Recommended Actions
Review the records for annulation-amazon.com from Google Safe Browsing, Phishunt, and VirusTotal to inform any ongoing monitoring. Preserve the exact detection counts and blocklist listings for future comparison with subsequent updates. Maintain a record of these source observations for reference in any further assessment.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
저장된 은신 플래그
아직 스캔되지 않았습니다
마지막 은폐 스캔
스캐너 메모:unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='annulation-amazon.com', port=80): Max retries exceeded with url: / (Caused by NewConnectio
TDS 지문 인식 실시간 확인
이 패널이 열려 있을 때 PhishDestroy 스캐너에서 실행되는 7개의 케이타로 지문과 크롤러 대 브라우저 비교 결과.
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Latest HTTP observation알 수 없음Probe Inconclusive20%2026-10-11 10:08:18 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-10 22:08:11 UTClast content: 2026-10-10 22:08:11 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.
Google PageSpeed Insights — mobile performance audit of annulation-amazon.com· checked Oct 6, 2026
100
Good
Performance
FCP
0.76s
First Contentful Paint
LCP
1.54s
Largest Contentful Paint
CLS
0
Cumulative Layout Shift
TBT
0ms
Total Blocking Time
SI
1.32s
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.
Status Check2026-10-06 21:12:12 UTC
Telemetry event observed.
Threat First Observed2026-10-06 21:11:38 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 172.236.104.157.
위협 대응 Pipeline
발견
Analysis
Monitoring
10 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.
(NL)
