← Back to Scanner

elastic.co

Name: elastic.co Email Security Posture Assessment
Creator: RacterMX

Posture Score: 81/100

Scanned May 8, 2026 at 4:24 PM UTC

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.elastic.co/.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 CAA records found

No CAA records are configured. Any certificate authority can issue certificates for this domain.

💡 Add CAA records to restrict certificate issuance. Example: 0 issue "letsencrypt.org"

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@elastic.co").

low

Slow DNS response from ns-339.awsdns-42.com: 2075.7ms

The nameserver ns-339.awsdns-42.com responded in 2075.7ms, exceeding the 500ms threshold.

💡 Investigate network latency or performance issues on ns-339.awsdns-42.com.

low

Very low TTL on MX records: 270s

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

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

low

Very low TTL on TXT records: 270s

29 TXT records have a TTL of 270s or less (below 300s).

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

low

Very low TTL on SPF record: 270s

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

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

low

Very low TTL on DMARC record: 270s

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

💡 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

DKIM cryptographic configuration is compliant

No RFC 8301 compliance issues detected in DKIM key configuration.

pass

No deprecated DMARCbis tags present

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

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

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

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

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

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: 7200s, Retry: 900s, Expire: 1209600s, Min TTL: 86400s

informational

Attack Surface Findings

DNS ANY query returns 42 record(s)

The DNS server responds to ANY queries with 42 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

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 elastic.co

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

informational

Reputation Findings

HSTS enabled but missing preload directive on elastic.co

Strict-Transport-Security: max-age=31536000; includeSubDomains

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

low

security.txt present

Found security.txt at https://elastic.co/.well-known/security.txt.

pass

TLS certificate valid for 73 days

Certificate for elastic.co expires on 2026-07-20.

pass

Certificate issued by R12

The certificate for elastic.co is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for elastic.co uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for elastic.co uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for elastic.co contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on elastic.co.

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.elastic.co

HTTPS request to https://webmail.elastic.co failed or timed out.

informational

WHOIS lookup failed

Could not retrieve WHOIS data for elastic.co.

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: ig-in-f26.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.27 → PTR Record Reverse DNS: yugrqzs-in-f27.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.26 → PTR Record Reverse DNS: lcfrai-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.26 → PTR Record Reverse DNS: rb-in-f26.1e100.net

Mail Server Reputation: aspmx.l.google.com