DomainGuard · Proof Card
Proof Card: getingeniousai.com
A standardized summary of one DomainGuard impersonation-exposure scan — what was assessed, exactly what was checked, what was found, and what to do next. Forward it to your team or IT provider; the complete report is linked below.
getingeniousai.com · Verdict: Exposed
DomainGuard exposure score (0–100; higher = less exposure found in the checks below) — a scan result, not a certification
Assessed 2026-11-10T03:19:22.558369Z · Scan DG-0B1IUIVKRF
Checks performed
0 certificate(s) currently logged for this domain in public CT logs (via crt.sh).
801 of 801 generated lookalike permutations checked for registration (DNS A / AAAA / NS / MX); 13 registered lookalike(s) found.
No CAA records published — any certificate authority may issue for this domain.
Evidence found
Publish a CAA record (e.g. 0 issue "letsencrypt.org") so only your CA can issue.
Top: gEtingeniousai.com, geTingeniousai.com, getIngeniousai.com, getiNgeniousai.com, getingEniousai.com, getingenIousai.com, getinGeniousai.com, getingeNiousai.com
Registered lookalikes (top 13)
| Domain | Technique | MX records |
|---|---|---|
| gEtingeniousai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| geTingeniousai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getIngeniousai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getiNgeniousai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getingEniousai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getingenIousai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getinGeniousai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getingeNiousai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getingeniOusai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getingeniouSai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getingeniousAi.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getingenioUsai.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
| getingeniousaI.com | bitsquatting | 20 route3.mx.cloudflare.net., 26 route1.mx.cloudflare.net., 70 route2.mx.cloudflare.net. |
13 of these publish mail (MX) records.
CAA posture
No CAA records published — any certificate authority may issue for getingeniousai.com.
Scope & limitations
What was NOT checked: the content actually hosted on the lookalike domains (phishing-kit scanning is a Pro check); your own DMARC / SPF / DKIM enforcement; anything behind a login, your inbox security, or malware already inside your site.
- One-time snapshot at the assessment date above — registrations and certificates change after it.
- Detection is rule-based and heuristic over public data (CT logs, DNS records); cloaked phishing kits can hide from any scanner, so a clean card is not a guarantee.
How this scan works — sources, checks and verification, in full.
Recommended next action
Why it matters: Any certificate authority may issue a trusted certificate for getingeniousai.com, so a phishing copy of your site can get a working padlock.
Fix:
Publish this DNS record with your registrar, naming YOUR certificate provider instead of the example if you use a different one: getingeniousai.com. 3600 IN CAA 0 issue "letsencrypt.org"
Retest status
Re-scan watch is on for this scan. A free re-scan runs 7 days after the report was captured by email, and its result is emailed to the watcher — the existing DomainGuard re-check, unchanged.