VirusTotal
14 / 91
“uaamaoi.garden | 522: Connection timed out”
Security analysis of uaamaoi.garden covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
The detailed PhishDestroy AI analysis below remains in English to preserve the original forensic record.
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.
Stored crawler-versus-browser observations for this host, plus a live fingerprint check for Keitaro-style traffic distribution systems.
cloudflareScanner note: redirect: raw=redirect_301; http=301; via=http_proxy; location=https://uaamaoi.garden/; server=cloudflare
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.
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.
Edge-IP reputation is not attributed to this domain.
coraline.ns.cloudflare.comnoel.ns.cloudflare.comLocation describes the IP network.
32d9c5aef78109b8092a6c00b007d5202e64958950ef0bbc8369231e8f8cda0eSaved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
13 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
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.
Capture the rendered page, requests and visible infrastructure.
Compare the available engine results and retain the analysis timestamp.
Check whether Google currently lists the URL as unsafe.
Inspect a public scan and its recorded network and classification data.
Look for indicator references and related community intelligence.
Compare archived captures and preserve historical context.
Look for matching indicators and associated threat records.
Inspect certificate records and related hostnames.
Compare security resolver responses and record observed blocking.
Inspect the public DNS, TLS, HTTP and technology surface.
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.
Reported by 1 community member, first seen Dec 20, 2025
If credentials, payment data, or files were exposed, report the incident immediately. Change affected passwords, revoke active sessions, and scan the device.
Select your country to get official cybercrime contacts, or create a complaint draft →.
Template-based draft · optional AI wording assistance requires separate consent
Threat analysis using stored blocklist, WHOIS, DNS, and public scan evidence
Scan NowSubmit suspicious domains to our threat database — protect the community
ReportRecent phishing reports and observed availability changes
MonitorMonitor live threats or contest this listing if you believe it's a false positive