The domain uaamaoi.garden was registered on December 17 2025 through the registrar Spaceship, Inc. It currently resolves to the IPv6 address 2a06:98c1:3121::3, which is announced by AS13335 Cloudflare, Inc. and therefore resides in the United States. The authoritative nameservers are coraline.ns.cloudflare.com and noel.ns.cloudflare.com, confirming that the domain is fully hosted on Cloudflare’s edge network and is served over HTTP/3. An HTTP 301 redirect is observed, and the TLS certificate presented is issued by Google Trust Services under the WE1 root, indicating a valid certificate chain. The page title returned by the server is “uaamaoi.garden | 522: Connection timed out”, suggesting that the backend service is currently unavailable or deliberately returning a timeout response. Threat intelligence flags this domain as a high‑risk generic phishing site.
It appears on one public security blocklist and is actively blocked by the PhishDestroy sink‑hole. VirusTotal scans have identified it as malicious in 14 of 95 antivirus engines, reinforcing the phishing classification. The Gridinsoft trust score is 0 out of 100, further indicating a lack of trustworthiness. No additional contextual information such as targeted brands or specific phishing kits has been disclosed; the content of the site beyond the timeout title has not been captured.
Defenders should treat any traffic to uaamaoi.garden as hostile. Immediate mitigation steps include adding the domain and its IPv6 address to outbound deny lists, updating web‑proxy and DNS filtering policies to block the domain, and ensuring that endpoint protection solutions incorporate the VirusTotal detection count. Continuous monitoring of the Cloudflare nameservers for any changes and periodic re‑scanning with VirusTotal are recommended, as the infrastructure may be repurposed.
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.
Latest HTTP observationRedirectingHTTP redirect observed80%2026-10-14 10:11:38 UTC
RDAP registration未知
Observed timelinelast reachable: 2026-10-14 10:11:38 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.
技术 · 2 identified
Cloudflare
CDN
Web infrastructure and security company providing CDN, DDoS mitigation, and DNS services.
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.
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)
