← Back to Scanner

forgerock.com

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

Posture Score: 74/100

Scanned May 8, 2026 at 4:55 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

SPF exceeds 10-lookup limit (21 lookups)

RFC 7208 limits SPF to 10 DNS lookups. Exceeding this causes PermError and SPF failures.

💡 Flatten your SPF record by replacing includes with direct ip4/ip6 mechanisms.

high

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 '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

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

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

Subdomain policy (sp=none) is weaker than domain policy (p=quarantine)

The subdomain policy is less restrictive than the organizational domain policy, leaving subdomains more vulnerable.

💡 Set sp=quarantine or remove sp= to inherit the domain policy.

medium

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.forgerock.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

SOA expire value too short

The SOA expire value is 259200s (<604,800s / 7 days). Secondary nameservers may stop serving the zone prematurely.

💡 Increase the SOA expire value to at least 604800 seconds (7 days).

medium

Void lookup: include:_spf.acquia.com

The mechanism include:_spf.acquia.com returns no records, wasting a DNS lookup.

💡 Remove mechanisms that reference non-existent domains.

low

DMARC percentage is 0% (not fully enforced)

Only 0% of messages are subject to the DMARC policy. The remaining messages are treated as p=none.

💡 Increase pct to 100 once confident in SPF/DKIM alignment.

low

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@forgerock.com").

low

Very low TTL on TXT records: 279s

23 TXT records have a TTL of 279s or less (below 300s).

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

low

Very low TTL on SPF record: 279s

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

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

low

Very low TTL on DMARC record: 279s

The DMARC record has a TTL of 279s 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 (~7179s) differs significantly from the authoritative zone (~21600s).

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

low

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

ARC support likely available

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

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

DNS responses are consistent across all nameservers

All authoritative nameservers return consistent answers with proper AA flags.

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

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

Deprecated DMARCbis tags found: pct

The DMARC record contains tags deprecated in DMARCbis: pct. Consider removing these for forward compatibility.

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

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

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

informational

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

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

informational

No DANE/TLSA records found

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

informational

No BIMI record found

BIMI is not configured. Your brand logo will not display in supporting email clients.

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 5 different /16 networks, providing good diversity.

informational

SOA record parameters

Serial: 1, Refresh: 21600s, Retry: 3600s, Expire: 259200s, Min TTL: 300s

informational

Authorized certificate authorities

CAA records restrict certificate issuance to: amazonaws.com, digicert.com, letsencrypt.org, pki.goog, sectigo.com

informational

Attack Surface Findings

Weak DNSSEC RSA key: 336 bits

The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.

💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.

high

Weak DNSSEC RSA key: 336 bits

The DNSKEY uses an RSA key of 336 bits, below the recommended 2048 bits.

💡 Generate a new DNSKEY with at least 2048-bit RSA or migrate to ECDSA/Ed25519.

high

DNS ANY query returns 52 record(s)

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

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

medium

Domain enumerability: low

The domain has low enumerability. Proper NSEC3 configuration and limited CT exposure reduce the attack surface.

low

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 forgerock.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 forgerock.com and its subdomains. Each certificate reveals subdomain names.

informational

NSEC3 authenticated denial of existence

The domain uses NSEC3 with 1 iteration(s) and salt '4B2D03B9A7F978BA'.

informational

DNSSEC is enabled

DNSKEY and/or DS records are present, indicating DNSSEC is configured.

informational

Reputation Findings

HSTS enabled but missing preload directive on forgerock.com

Strict-Transport-Security: max-age=31557600

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

low

security.txt present

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

pass

TLS certificate valid for 75 days

Certificate for forgerock.com expires on 2026-07-22.

pass

Certificate issued by Amazon RSA 2048 M03

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

pass

Signature algorithm: rsa-sha256

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

pass

RSA key: 2048 bits

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

pass

SCTs present in certificate

The certificate for forgerock.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on forgerock.com.

pass

Domain valid for 145 days

Domain forgerock.com expires on 2026-09-30.

pass

Domain transfer and delete locks enabled

Domain forgerock.com has clientTransferProhibited and clientDeleteProhibited locks.

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.forgerock.com

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

informational

WHOIS registration data

Registrar: GoDaddy.com, LLC | Created: 2009-09-30 | Expires: 2026-09-30 | Updated: 2025-10-01

informational

WHOIS privacy protection enabled

Domain forgerock.com has WHOIS privacy/redaction enabled.

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: quarantine

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: quarantine

⚠️ 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 74.125.193.26 → PTR Record Reverse DNS: di-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: alt3.aspmx.l.google.com

PTR record proves mail server legitimacy

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

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

PTR record proves mail server legitimacy

MX: alt4.aspmx.l.google.com Mail server at 142.251.127.27 → PTR Record Reverse DNS: lcfrai-in-f27.1e100.net

Mail Server Reputation: aspmx.l.google.com