The domain www.usdt-qr-code-generator.com is currently active and resolves to the IPv4 address 216.198.79.1, which belongs to Amazon.com, Inc. (AS16509) and is geolocated in the United States. Registration information shows the domain was created on May 15, 2026 through TUCOWS.COM, CO., and it is served by the njalla name servers (1-you.njalla.no, 2-can.njalla.in, 3-get.njalla.fo). The site presents a valid TLS certificate issued by Let’s Encrypt (R13) and advertises HSTS support; infrastructure analysis also identifies Vercel as the hosting platform. VirusTotal reports that 13 of 91 security vendors have flagged the domain, and Gridinsoft assigns a trust score of 0 out of 100. The page returns HTTP 200 and carries the title "USDT QR Code Generator — Create Free Tether QR with Logo," indicating a likely attempt to lure users into generating fraudulent USDT QR codes. The domain is listed on one security blocklist and has been blocked by PhishDestroy. Defenders should treat this domain as high‑risk: block the domain and its resolved IP at perimeter firewalls, add the associated name servers to block lists, and monitor for any outbound connections to the host. Network logging should be enriched to capture attempts to access this URL, and incident response teams should be alerted to any user reports of unsolicited QR‑code generation prompts. Continuous threat‑intel feeds should be consulted for any new indicators tied to this infrastructure, and user education programs should warn against interacting with unsolicited QR‑code generators claiming to create USDT payment codes.
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='duplicate-disabled-223068.invalid', port=80): Max retries exceeded with url: / (Caused by
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.
Keep original emails, receipts, messages and screenshots in a secure place. A factual timeline helps the receiving authority understand what happened. IC3 evidence guidance ↗
Payment records — if you paid, save the receipt, amount, date, payment provider and recipient details.
Your bank or payment provider — contact its fraud team promptly through official contact details if money or card information was exposed.
地元の警察 — たとえ直ちに行動を起こせなくても、公式な記録が残される
A report is not a guarantee of recovery or investigation, but prompt, accurate transaction data can help authorities and service providers trace the incident.
詐欺による金銭の返還を装った詐欺 — fraudsters pose as recovery agents and demand upfront fees. Never share a seed phrase or pay before independently verifying the provider
About this reportSources, observation dates and corrections
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.
(KN)
