← Back to Scanner

gemini.com

Name: gemini.com Email Security Posture Assessment
Creator: RacterMX

Posture Score: 77/100

Scanned May 10, 2026 at 4:46 PM UTC

Score History

Identity

Attack Surface

Reputation

Identity Findings

Weak DKIM RSA key (~1296 bits) for selector 'google'

RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.

💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.

high

Weak DKIM RSA key (~1296 bits) for selector 'k1'

RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.

💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.

high

Weak DKIM RSA key (~1296 bits) for selector 's2'

RSA keys shorter than 2048 bits are considered weak. Current key is approximately 1296 bits.

💡 Generate a new 2048-bit (or larger) RSA key pair and update the DKIM record.

high

No MTA-STS record found

Without MTA-STS, mail transport encryption cannot be enforced and is vulnerable to downgrade attacks.

💡 Publish a _mta-sts TXT record and host a policy file at https://mta-sts.gemini.com/.well-known/mta-sts.txt

medium

STARTTLS without MTA-STS or DANE protection

STARTTLS alone is vulnerable to downgrade attacks. Neither MTA-STS nor DANE is configured to enforce encryption.

💡 Deploy MTA-STS and/or DANE to protect against STARTTLS stripping attacks.

medium

No TLS-RPT record found

Without TLS-RPT, you will not receive reports about TLS negotiation failures.

💡 Publish a _smtp._tls TXT record (e.g. "v=TLSRPTv1; rua=mailto:tls-reports@gemini.com").

low

Shared IP 142.250.102.27 used by multiple MX servers

The IP 142.250.102.27 is shared across 2 MX hostnames, reducing redundancy.

💡 Use unique IP addresses for each MX server for better redundancy.

low

Slow DNS response from ns-456.awsdns-57.com: 2076.2ms

The nameserver ns-456.awsdns-57.com responded in 2076.2ms, exceeding the 500ms threshold.

💡 Investigate network latency or performance issues on ns-456.awsdns-57.com.

low

Very low TTL on MX records: 28s

5 MX records have a TTL of 28s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on SPF record: 28s

The SPF record has a TTL of 28s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on TXT records: 28s

32 TXT records have a TTL of 28s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

Very low TTL on DMARC record: 29s

The DMARC record has a TTL of 29s or less (below 300s).

💡 Increase the TTL to at least 300 seconds unless frequent changes are expected.

low

NS TTL mismatch between parent and authoritative zone

The NS record TTL in the parent zone (~7169s) differs significantly from the authoritative zone (~172800s).

💡 Align NS record TTLs between the parent zone delegation and the authoritative zone.

low

SPF record is valid

The SPF record is properly configured with valid syntax and within lookup limits.

pass

SPF record length OK (162 bytes)

SPF record is within safe DNS packet size limits.

pass

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

DKIM key strength indicates modern key management

All DKIM keys use RSA-2048+ or Ed25519, consistent with current best practices.

pass

All external report destinations authorized

External DMARC report destinations have valid authorization records per RFC 7489 §7.1.

pass

Subdomains protected (sp=reject)

DMARC subdomain policy enforces quarantine or reject on unauthenticated subdomain mail.

pass

No deprecated DMARCbis tags present

The DMARC record does not use any tags deprecated in DMARCbis (pct, rf, ri).

pass

5 MX records with 4 unique IPs

Multiple MX records provide mail delivery redundancy.

pass

BIMI record is valid

BIMI is properly configured with a valid logo and DMARC enforcement.

pass

ARC support likely available

MX server software appears to support ARC headers for authentication preservation.

pass

Meets bulk sender authentication requirements

Domain has SPF, DKIM, and DMARC — meeting Google/Yahoo 2024 bulk sender requirements for email authentication.

pass

SMTP security checks passed

No open relay, VRFY/EXPN, or banner disclosure issues detected.

pass

SMTP RFC 5321 compliance checks passed

The mail server accepts postmaster@ and abuse@ and uses a valid FQDN in EHLO.

pass

IPv6 readiness is good

IPv6 records are present and properly configured.

pass

NS delegation is properly configured

All nameservers are responsive, consistent, and properly secured.

pass

DKIM2 not detected

No DKIM key record with v=2 was found across common selectors. DKIM2 is an emerging standard and not yet widely deployed.

informational

DMARC alignment: adkim=r, aspf=r

DKIM alignment is relaxed, SPF alignment is relaxed.

informational

DMARC failure reporting: fo=1

Failure reports generated when any authentication mechanism fails.

informational

DMARCbis np tag absent

The DMARC record does not include the np (non-existent subdomain policy) tag. Consider adding np=reject to protect non-existent subdomains under DMARCbis.

informational

DMARCbis psd tag absent

The DMARC record does not include the psd (public suffix domain) indicator. Consider adding psd=n to explicitly identify this as an organizational domain.

informational

Shared/free email hosting detected: aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt1.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

Shared/free email hosting detected: alt2.aspmx.l.google.com

The MX record points to a known shared or free email hosting provider.

informational

REQUIRETLS not advertised

The primary MX does not advertise REQUIRETLS (RFC 8689). This is an emerging standard — MTA-STS and DANE provide adequate TLS enforcement for most deployments.

informational

No DANE/TLSA records found

DANE is not configured for any MX server. This is optional but provides strong certificate binding.

informational

No VMC authority URL in BIMI record

The BIMI record does not specify a VMC (a= tag). Gmail and Apple Mail require a VMC to display brand logos.

informational

Open mail ports on aspmx.l.google.com

Detected open mail-related ports: 25

informational

RFC 8058 one-click unsubscribe assessment

DKIM signing is configured. RFC 8058 compliance depends on List-Unsubscribe and List-Unsubscribe-Post headers being included in outbound messages and DKIM signatures.

informational

MX IP network diversity

MX IPs span 3 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 1, Refresh: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s

informational

Authorized certificate authorities

CAA records restrict certificate issuance to: amazon.com, digicert.com, globalsign.com, letsencrypt.org, pki.goog

informational

Attack Surface Findings

DNS ANY query returns 53 record(s)

The DNS server responds to ANY queries with 53 record(s), creating significant DNS amplification risk.

💡 Configure the DNS server to refuse or minimize ANY query responses per RFC 8482.

medium

Domain enumerability: medium

The domain has moderate enumerability. CT logs and DNS records reveal significant information about the domain structure.

💡 Restrict zone transfers, use NSEC3 instead of NSEC, consider wildcard certificates to reduce CT log exposure, and implement rate limiting on DNS queries.

medium

DNSSEC is not enabled

No DNSKEY or DS records were found. DNS responses are not cryptographically authenticated.

💡 Enable DNSSEC by generating DNSKEY records and publishing DS records at the registrar.

medium

All MX records resolve correctly

No dangling MX records detected — all MX hostnames resolve to valid IP addresses.

pass

Explicit MX records present

The domain has explicit MX records — no implicit A-record fallback delivery.

pass

No internal information leakage detected

No non-routable IP addresses or internal references were found in public DNS records.

pass

No email autodiscovery endpoints detected

No Microsoft Autodiscover, Mozilla Autoconfig, or email SRV records were found.

pass

8 subdomain(s) discovered for gemini.com

Subdomains were enumerated via Certificate Transparency logs, DNS wordlist brute-forcing, and DNS record analysis.

informational

0 certificate(s) found in CT logs

Certificate Transparency logs contain 0 certificate(s) for gemini.com and its subdomains. Each certificate reveals subdomain names.

informational

Reputation Findings

Missing domain locks: clientDeleteProhibited

Domain gemini.com is missing protective locks: clientDeleteProhibited.

💡 Enable clientTransferProhibited and clientDeleteProhibited locks through your registrar to prevent unauthorized transfers or deletions.

high

SMTP banner mismatch: mx.google.com

The SMTP banner identifies as 'mx.google.com' but the MX hostname is 'aspmx.l.google.com' and PTR resolves to 'ig-in-f26.1e100.net'. Microsoft and other receivers flag this mismatch as suspicious infrastructure.

💡 Configure the SMTP server banner to match the MX hostname or PTR record (aspmx.l.google.com).

high

HSTS enabled but missing preload directive on gemini.com

Strict-Transport-Security: max-age=31536000

💡 Add the "preload" directive to the HSTS header and submit the domain to hstspreload.org.

low

security.txt present

Found security.txt at https://gemini.com/.well-known/security.txt.

pass

TLS certificate valid for 155 days

Certificate for gemini.com expires on 2026-10-12.

pass

Certificate issued by Amazon RSA 2048 M01

The certificate for gemini.com is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for gemini.com uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for gemini.com uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for gemini.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on gemini.com.

pass

Domain valid for 1376 days

Domain gemini.com expires on 2030-02-15.

pass

TLD has good reputation

The .com TLD is not on known abuse watchlists.

pass

DMARC reporting destinations look legitimate

DMARC rua/ruf addresses do not point to known URL shortener services.

pass

MX records point to stable infrastructure

No MX records point to known dynamic DNS service domains.

pass

Strong TLS configuration on primary MX

Primary MX (aspmx.l.google.com) uses TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 including Forward Secrecy.

pass

Google Safe Browsing DNS check — no flag detected

DNS-based Safe Browsing lookup returned no results. Full verification requires the Google Safe Browsing API key.

informational

Abuse contact lookup failed

Could not query abuse contact information.

informational

PhishTank — API key required

PhishTank phishing database check requires an API key.

informational

Sender Score — API key required

Sender Score reputation check requires an API key.

informational

Cisco Talos — API key required

Cisco Talos IP reputation check requires an API key.

informational

Could not connect to webmail.gemini.com

HTTPS request to https://webmail.gemini.com failed or timed out.

informational

WHOIS registration data

Registrar: Gandi SAS | Created: 1994-02-14 | Expires: 2030-02-15 | Updated: 2026-02-06

informational

WHOIS privacy protection enabled

Domain gemini.com has WHOIS privacy/redaction enabled.

informational

Typosquat detected: emini.com (has MX!), gmini.com (has MX!), geini.com (has MX!), gemni.com (has MX!), gemii.com (has MX!)

25 registered lookalike domain(s) that could be used for phishing against your brand. Showing top 5 of 25. Domains with MX records can send and receive email, making them high-risk phishing vectors.

informational

Dependency Chains

DMARC Authentication Chain (SPF)

DMARC uses SPF to verify that emails come from authorized servers

SPF Record SPF record found and configured → DMARC Policy DMARC policy: reject

DMARC Authentication Chain (DKIM)

DMARC uses DKIM to verify that emails have not been tampered with

DKIM Signature DKIM signature missing → DMARC Policy DMARC policy: reject

⚠️ DKIM signature is missing. DMARC relies on DKIM to verify email integrity and prevent tampering. Without DKIM, DMARC alignment will fail for cryptographic verification.

Mail Server Identity: aspmx.l.google.com

PTR record proves mail server legitimacy

MX: aspmx.l.google.com Mail server at 172.253.116.26 → PTR Record Reverse DNS: dj-in-f26.1e100.net

Mail Server Identity: alt1.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt1.aspmx.l.google.com Mail server at 173.194.76.27 → PTR Record Reverse DNS: ws-in-f27.1e100.net

Mail Server Identity: alt2.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt2.aspmx.l.google.com Mail server at 142.250.102.27 → PTR Record Reverse DNS: rb-in-f27.1e100.net

Mail Server Identity: aspmx2.googlemail.com

PTR record proves mail server legitimacy

MX: aspmx2.googlemail.com Mail server at 173.194.76.26 → PTR Record Reverse DNS: ws-in-f26.1e100.net

Mail Server Identity: aspmx3.googlemail.com

PTR record proves mail server legitimacy

MX: aspmx3.googlemail.com Mail server at 142.250.102.27 → PTR Record Reverse DNS: rb-in-f27.1e100.net

Mail Server Reputation: aspmx.l.google.com