VirusTotal
14 / 91 engine detections
Bericht öffnen“uaamaoi.garden | 522: Connection timed out”
Security analysis of uaamaoi.garden covers observed phishing indicators, infrastructure evidence, current status, and defensive guidance.
Die ausführliche Analyse von PhishDestroy AI bleibt auf Englisch, damit der ursprüngliche forensische Bericht unverändert bleibt.
14 / 91 engine detections
Bericht öffnen24 community references
Bericht öffnenprovider verdict: clean
Bericht öffnenNo threat flag
Bericht öffnenNo malicious flag
Bericht öffnenResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
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.
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.
Die Edge-IP-Reputation wird dieser Domäne nicht zugeordnet.
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
redirect: raw=redirect_301; http=301; via=http_proxy; location=https://uaamaoi.garden/; server=cloudflare
uaamaoi.garden
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Unbekannt→redirected
http_redirect
Nicht verfügbar→Erreichbar
https://radar.cloudflare.com/scan/50ede442-5309-4e96-883e-441cebfb3b5c
Erreichbar→Nicht verfügbar
https://radar.cloudflare.com/scan/5ea134c6-92d1-4235-8623-28a91c60b9f6
No threat flag
View source24 community references
View source14/91 engine detections
View sourcePage captured
View sourceuaamaoi.garden
View sourceVon 1 Community-Mitglied gemeldet; erstmals gesehen am 20.12.2025
Listed domains receive at least one abuse report; this entry has no retained notification history.
Wenn Sie Kontoanmeldeinformationen, persönliche oder Zahlungsinformationen eingegeben oder eine Datei von dieser Domain heruntergeladen haben, ergreifen Sie sofort Maßnahmen. Nachfolgend finden Sie Ressourcen, die Ihnen helfen, den Vorfall zu melden und sich zu schützen.
Wählen Sie Ihr Land aus, um Offizielle Kontakte im Bereich Cyberkriminalität oder einen Beschwerdeentwurf erstellen → zu erhalten.
Template-based draft · optional AI wording assistance requires separate consent
Choose the steps that match what you shared. Keep a copy of this report alongside your own records.
Stop using the suspicious site. Open the real service through its official app or an address you already trust.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
uaamaoi.garden)Auch wenn dir nicht alle Details bekannt sind — trotzdem Anzeige erstatten. Auch unvollständige Informationen sind für die Ermittlungen hilfreich.
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
Further guidance: NIST · phishing responseFBI IC3 · reports & evidenceFTC · recovery scams
Bedrohungsanalyse anhand gespeicherter Blocklisten, WHOIS, DNS und öffentlicher Scan-Beweise
Jetzt scannenMelden Sie verdächtige Domains an unsere Bedrohungsdatenbank – schützen Sie die Community
MeldenAktuelle Phishing-Meldungen und beobachtete Verfügbarkeitsänderungen
ÜberwachenBeobachten Sie aktuelle Bedrohungen oder legen Sie Widerspruch gegen diesen Eintrag ein, wenn Sie der Meinung sind, dass es sich um einen Fehlalarm handelt
This report combines saved page captures, registration and network records, scanner results and PhishDestroy reporting history. Each source keeps its own observation date. Open a source report to inspect the original result.
The AI-assisted analysis was written on . It describes the evidence available at that time; later source checks can change.
A capture documents what was shown. A scanner result records that provider’s assessment at the time of its check. Neither a valid certificate nor a zero-detection result is a guarantee of safety.