← Back to Scanner

logz.io

Name: logz.io Email Security Posture Assessment
Creator: RacterMX

Posture Score: 87/100

Scanned May 8, 2026 at 5:20 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 '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

NS delegation mismatch

The registrar-delegated nameservers do not match the zone NS records.

💡 Update either the registrar NS delegation or the zone NS records to match.

high

SPF has ip4 mechanisms but no ip6

The SPF record authorizes IPv4 addresses but not IPv6. Your MX servers have AAAA records, so IPv6 mail delivery is possible without SPF authorization.

💡 Add ip6: mechanisms to the SPF record for your IPv6 mail server addresses.

low

No CAA iodef tag configured

No iodef tag is present in the CAA records. CA policy violation reports will not be sent.

💡 Add an iodef CAA record. Example: 0 iodef "mailto:security@example.com"

low

Very low TTL on DMARC record: 41s

The DMARC record has a TTL of 41s 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 (~7181s) 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

MTA-STS and TLS-RPT are properly configured

MTA-STS policy is enforced and TLS reporting is configured.

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

STARTTLS downgrade resistance is adequate

STARTTLS is supported with modern TLS and protected by MTA-STS and/or DANE.

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=s, aspf=s

DKIM alignment is strict, SPF alignment is strict.

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: alt2.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: alt4.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

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: 2019123465, Refresh: 3600s, Retry: 600s, Expire: 604800s, Min TTL: 300s

informational

Authorized certificate authorities

CAA records restrict certificate issuance to: digicert.com, letsencrypt.org, amazontrust.com, sectigo.com, akamai.net, amazonaws.com, amazon.com, awstrust.com

informational

Attack Surface Findings

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

DNS ANY query returns 1 record(s)

The DNS server responds to ANY queries with 1 record(s). The low record count limits amplification risk, but ANY responses still aid reconnaissance.

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

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

5 subdomain(s) discovered for logz.io

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

informational

Reputation Findings

HSTS enabled but missing preload directive on logz.io

Strict-Transport-Security: max-age=31622400

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

low

security.txt present

Found security.txt at https://logz.io/.well-known/security.txt.

pass

TLS certificate valid for 70 days

Certificate for logz.io expires on 2026-07-18.

pass

Certificate issued by R12

The certificate for logz.io is issued by a third-party CA.

pass

Signature algorithm: rsa-sha256

The certificate for logz.io uses an acceptable signature algorithm.

pass

RSA key: 2048 bits

The certificate for logz.io uses an adequate RSA key of 2048 bits.

pass

SCTs present in certificate

The certificate for logz.io contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on logz.io.

pass

Domain valid for 160 days

Domain logz.io expires on 2026-10-16.

pass

Domain transfer and delete locks enabled

Domain logz.io 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.logz.io

HTTPS request to https://webmail.logz.io failed or timed out.

informational

WHOIS registration data

Registrar: GoDaddy.com, LLC | Created: 2014-10-16 | Expires: 2026-10-16 | Updated: 2024-07-05

informational

WHOIS privacy protection enabled

Domain logz.io 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: 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.27 → PTR Record Reverse DNS: dj-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 Identity: alt1.aspmx.l.google.com

PTR record proves mail server legitimacy

MX: alt1.aspmx.l.google.com Mail server at 173.194.76.26 → PTR Record Reverse DNS: ws-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 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 Reputation: aspmx.l.google.com