angliving.shop was observed returning an HTTP 200 response on 2026-10-06, indicating a successful connection at that time. The domain also received a PageSpeed performance score, offering insight into its technical characteristics.
Recorded Evidence
VirusTotal scanned angliving.shop on 2026-10-06, recording 7 detections out of 92 scanners. OTX referenced the domain in 2 pulses on the same date. The domain was listed internally by PhishDestroy as of 2026-10-06. PageSpeed assigned a performance score of 78 on 2026-10-06.
Interpretation
The collected evidence from VirusTotal, OTX, PageSpeed, and PhishDestroy provides multiple perspectives on angliving.shop's recorded status. Each source supplies distinct information, such as security findings, community references, performance data, and internal cataloging. The matching observation dates allow for direct comparison of these records without indicating any progression or trend.
Recommended Actions
For angliving.shop, it is advisable to review VirusTotal and OTX records for further details and monitor for future updates. Retain the HTTP response and PageSpeed score as technical references. Preserve the PhishDestroy internal listing as a catalog entry and compare it with subsequent records to track any changes.
DOM Analysisanalyzed 2026年10月9日score 83/1002 brand signals
Submitted URLhttp://angliving.shop/
Favicon Hash
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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-11 10:07:47 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:07:47 UTClast content: 2026-10-11 10:07:47 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.
使用技術 · 1 identified
H
HTTP/3
Miscellaneous
HTTP/3 is the third major version of the Hypertext Transfer Protocol used to exchange information on the World Wide Web.
Last analyzed Previous stored snapshot: 7 detections
alphaMountain.ai
BitDefender
ESET
G-Data
Gridinsoft
LevelBlue
Webroot
サイトパフォーマンス分析
Google PageSpeed Insights — mobile performance audit of angliving.shop· checked Oct 6, 2026
78
Needs Work
Performance
FCP
2.86s
First Contentful Paint
LCP
4.35s
Largest Contentful Paint
CLS
0.011
Cumulative Layout Shift
TBT
139ms
Total Blocking Time
SI
2.86s
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.
Domain Status Transition2026-10-09 01:47:48 UTC
Domain state transitioned from dead to alive.
Domain Status Transition2026-10-06 10:00:26 UTC
Domain state transitioned from alive to dead.
Threat First Observed2026-10-06 07:03:48 UTC
Domain ingestion complete. Initial state is marked as unknown pointing to IP 146.19.203.219.
脅威対応 Pipeline
ディスカバリー
Analysis
Monitoring
12 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.
(US)
