launchdarkly.com

Name: launchdarkly.com Email Security Posture Assessment
Creator: RacterMX
License: https://creativecommons.org/licenses/by-nc/4.0/

Posture Score: 87/100

Scanned May 27, 2026 at 6:20 PM UTC

Identity

Attack Surface

Reputation

Identity Findings

No NS records found

No nameserver records could be retrieved for this domain.

💡 Ensure NS records are properly configured at your registrar and in your zone file.

critical

Cannot check DNS consistency — no NS records

No nameserver records could be retrieved for consistency checking.

💡 Ensure NS records are properly configured.

high

SPF record is valid

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

pass

DKIM records are valid

DKIM records found and validated for selectors: selector1, salesforce, zendesk1, zendesk2

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

MTA-STS and TLS-RPT are properly configured

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

pass

TLS-RPT report destinations are reachable

All TLS-RPT rua= URIs point to resolvable domains.

pass

BIMI record is valid

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

pass

VMC URL is accessible

The BIMI VMC authority URL is reachable and returns a valid response.

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

STARTTLS downgrade resistance is adequate

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

pass

DNS TTL values follow best practices

All critical DNS record TTLs are within recommended ranges.

pass

SPF record is 261 bytes (multi-string TXT)

The SPF record exceeds 255 bytes and requires multi-string TXT encoding. Most modern resolvers handle this correctly.

informational

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

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

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

Authorized certificate authorities

CAA records restrict certificate issuance to: sectigo.com, letsencrypt.org, digicert.com, pki.goog, globalsign.com, amazon.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

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 excessive DNS information exposure detected

No HINFO, LOC, RP records, version disclosures, or zone walking vulnerabilities were found.

pass

No email autodiscovery endpoints detected

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

pass

7 subdomain(s) discovered for launchdarkly.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 launchdarkly.com and its subdomains. Each certificate reveals subdomain names.

informational

Reputation Findings

TLS certificate expires in 21 days

Certificate for launchdarkly.com expires on 2026-06-17 (21 days).

💡 Renew the TLS certificate soon — it expires within 30 days.

high

HSTS enabled but missing preload directive on launchdarkly.com

Strict-Transport-Security: max-age=31536000

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

low

Not listed on any DNS blacklists

Domain and MX IPs checked against 55 DNSBLs — no listings found.

pass

security.txt present

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

pass

Certificate issued by E8

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

pass

Signature algorithm: ecdsa-with-sha384

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

pass

ECC key: 256 bits

The certificate for launchdarkly.com uses an adequate ECC key of 256 bits.

pass

SCTs present in certificate

The certificate for launchdarkly.com contains Signed Certificate Timestamps.

pass

No weak ciphers detected

No known weak cipher suites detected on launchdarkly.com.

pass

No disposable email provider MX records

MX records for launchdarkly.com do not match known disposable email provider patterns.

pass

No wildcard MX records

No wildcard MX records detected for launchdarkly.com.

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

SMTP banner from hosted mail provider

The MX (aspmx.l.google.com) is a hosted mail service. Banner alignment is managed by the provider and not actionable by the domain owner.

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 contacts found for MX IPs

Abuse contact information retrieved via abusix.org DNS lookup.

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

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

informational

WHOIS lookup failed

Could not retrieve WHOIS data for launchdarkly.com.

informational

Could not determine domain age

WHOIS creation date could not be parsed for launchdarkly.com.

informational

Bulletproof Hosting Detection — API key required

Checking IPs against known bulletproof hosting providers requires a threat intelligence API key.

informational

Threat Intelligence Feeds — API key required

Checking domain against threat intelligence feeds requires API keys (e.g., VirusTotal, AbuseIPDB).

informational

Typosquat detected: lunchdarkly.com

1 registered lookalike domain(s) that could be used for phishing against your brand. 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 209.85.203.27 → PTR Record Reverse DNS: dh-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.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.27 → PTR Record Reverse DNS: rb-in-f27.1e100.net

Mail Server Reputation: aspmx.l.google.com