g-mail.digital is assessed as a high-risk domain for brand impersonation. This domain is designed to mimic Facebook, likely to deceive users into providing sensitive information such as login credentials or personal data. The risk level is high due to the domain's involvement in multiple threat intelligence reports and its current status of being flagged by security vendors.
Analysis indicates that g-mail.digital has been flagged in 17 threat intelligence pulses on AlienVault OTX, suggesting a significant level of malicious activity associated with the domain. VirusTotal reports that 21 out of 95 security vendors have flagged this domain, indicating a moderate level of consensus among security experts regarding its malicious nature. The domain is registered through Name.com, Inc and resolves to the IP address 16.16.167.230. It was created on November 30, 2025, which is a relatively recent date, often a common characteristic of malicious domains. Additionally, the domain appears on 2 security blocklists and lacks an SSL certificate, further raising concerns about its security and legitimacy. Google Safe Browsing has also flagged the domain for phishing, confirming the brand impersonation threat.
To mitigate the risk of brand impersonation associated with g-mail.digital, users should avoid clicking on any links or entering personal information on the site. Organizations should update their security policies to include this domain in their blocklists and educate employees about the dangers of brand impersonation attacks. Network administrators should monitor for any attempts to access this domain and implement DNS filtering to prevent access. Additionally, reporting the domain to the relevant brand (Facebook) and the domain registrar (Name.com, Inc) can help in taking further action to shut down the malicious activity and protect users.
DOM Analysisanalyzed 2026年4月23日score 25/1002 brand signals
Submitted URLhttp://g-mail.digital/
ICANN OVERSIGHT
認定と RAA の背景
Registrar accreditation and DNS abuse obligations
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.
Primary outcomeDNS 非アクティブreason: DNS NXDOMAIN80% confidence
Attributionsource: Dns Cache
Evidence layersAvailability: DNS inactiveContent: UnreachableDNS: NXDOMAINRegistration: Unknown
Latest HTTP observation不明Probe Inconclusive20%2026-10-19 01:08:48 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-06-16 10:49:47 UTCcurrent episode first observed: 2026-09-30 16:14:55 UTCobserved RIP window: 2026-06-16 10:49:47 UTC → 2026-09-30 16:14:55 UTC · 2,549.42hmidpoint estimate ≈ 2026-08-08 13:32:21 UTC · precision very low · basis bounded
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.
An estimated time describes an observation window. It does not prove a registrar action or the exact moment a site became unavailable.
Check for cloaking
Compare what a browser and a crawler receive, and check for Keitaro traffic routing.
No cloaking flag in this check
unavailable: raw=connection_error; http=0; via=http_proxy; error=SOCKSHTTPConnectionPool(host='g-mail.digital', port=80): Max retries exceeded with url: / (Caused by NewConnectionError(
g-mail.digital
Stored observation history11
Dated changes retained by the monitor and source collectors. Newest observations appear first; source states are not proof of a takedown.
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.
(US)
