VirusTotal
0 / 91
engines flag the domain
“USD AI”
The sent-report ledger records the first outgoing report at .
The recorded recipient is abuse@key-systems.net.
The latest stored availability evidence still shows the domain reachable; 23 days has elapsed since the first outgoing report.
ICANN RAA §3.18 describes registrar abuse-contact and handling obligations. This section records outgoing timestamps, listed recipients, case identifiers, and later availability. It does not by itself prove receipt, acknowledgement, investigation, remediation, or contractual non-compliance.
0 / 91
engines flag the domain
No threat flag
Not on Google threat lists at check time
No malicious flag
Browser scan with screenshot
0
threat pulses mention the domain
Online · HTTP 200
Cloudflare · 188.114.96.1 · TLS: Let's Encrypt
Each check shows its own collection time. Zero detections do not guarantee safety.
MetaMask taklidi: usdai.app — Bilinen son aktif (HTTP 301). Kanıt özeti: VirusTotal 4/92 (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft, SOCRadar)…
Özgün adli kaydı korumak için aşağıdaki ayrıntılı PhishDestroy AI analizi İngilizce bırakılmıştır.
4 / 92 engine detections
Raporu aç60 det.
Raporu aç4 community references
Raporu açprovider verdict: clean
Raporu açNo threat flag
Raporu açNo malicious flag
Raporu açResults reflect each source’s collection time. Zero detections do not guarantee safety. OTX references are community publications.
PhishDestroy threat report
usdai.app presents itself under the page title "USD AI" and is classified by PhishDestroy as an impersonation phishing page. Its targets are crypto users who believe they are dealing with the genuine USD AI project. PhishDestroy first flagged the domain on 2026-09-27, and as of 2026-10-19 the site was still online and serving its content.
Impersonation pages like this copy a project's name and look so visitors treat the site as the official one. Victims are then pushed toward an action that hands over control, usually connecting a wallet and signing a transaction or approval, or typing in a seed phrase or login details. Once that happens, the operators can move tokens out of the wallet or take over the account, and on-chain losses are rarely recoverable.
Wallet and security blocklists back the classification. MetaMask and SEAL list the domain alongside PhishDestroy, so MetaMask users should see a warning before the page loads. VirusTotal coverage is thin: on 2026-10-09 only 4 of 92 engines flagged it (alphaMountain.ai, Forcepoint ThreatSeeker, Gridinsoft and SOCRadar). A browser that relies on general-purpose scanners alone may let the page through. The domain also appears in 4 AlienVault OTX threat pulses.
The domain was registered on 2026-09-23 through Key-Systems LLC and was being reported four days later. That short gap is typical of throwaway domains set up for a single campaign. The site sits behind Cloudflare, with the address resolving to Canada, which masks where the real server is hosted. Its Let's Encrypt certificate gives it a padlock in the browser, but that only means the connection is encrypted, not that the site is legitimate.
If you connected a wallet to usdai.app, review and revoke any token approvals or permissions granted around that time with a reputable approval checker. Move remaining funds to a fresh wallet if you signed anything you did not fully understand. If you entered a seed phrase, treat that wallet as compromised and transfer its assets to a new one immediately. Reach USD AI only through links from its verified official channels, not search ads or direct messages. Security teams should block the domain at DNS and proxy level and check logs for visits since 2026-09-27.
Full extracted values, their blockchain and collection source. An address found in page content does not establish who controls it.
https://t.me/usdaiofficialStored page referenceIoC extraction recorded 2026-09-27 04:00:07 UTC
Last checked
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 itibarı bu etki alanıyla ilişkilendirilmez.
rene.ns.cloudflare.comrosalie.ns.cloudflare.comLocation describes the IP network.
65b214a6219c90fc33fdb8ad6453bd45c8e111cccfbf43cceab17c72f73367e6Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Google PageSpeed Insights — mobile performance audit of usdai.app · checked Sep 27, 2026
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://usdai.app/; server=cloudflare
usdai.app
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
Mevcut değil→Erişilebilir
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Bilinmiyor→inactive
http_no_content
Erişilebilir→Mevcut değil
Bilinmiyor→live_content
content_served
Bilinmiyor→live_content
content_served
0→1
No threat flag
View source4/92 engine detections
View source4 community references
View sourcePD-20260927-646644
Page captured
View sourceusdai.app
View source79 kayıtlı benzer alan adı
PD-20260927-646644 Recipient: abuse@key-systems.net Hesap kimlik bilgilerini, kişisel bilgileri veya ödeme bilgilerini girdiyseniz ya da bu alan adından bir dosya indirdiyseniz hemen harekete geçin. Aşağıda olayı bildirmenize ve kendinizi korumanıza yardımcı olacak kaynaklar bulunmaktadır.
resmi siber suç iletişim bilgileri veya şikayet taslağı oluştur → almak için ülkenizi seçin.
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 ↗
usdai.app)Tüm ayrıntıları bilmeseniz bile — yine de şikayette bulun. Kısmi bilgiler de soruşturmalara yardımcı olmaktadır.
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
Saklanan engelleme listesi, WHOIS, DNS ve genel tarama kanıtlarını kullanarak tehdit analizi
Şimdi TaraŞüpheli alan adlarını tehdit veritabanımıza bildirin — topluluğu koruyun
BildirSon kimlik avı raporları ve gözlemlenen kullanılabilirlik değişiklikleri
İzleCanlı tehditleri izleyin veya bunun yanlış bir uyarı olduğunu düşünüyorsanız bu kayda itiraz edin
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.