SurfaceMap › o › optimizely.com

optimizely.com

Checked 2026-10-22 10:10 UTC · first added 2026-10-21
!Passed with warnings Score 85 of 100

Domain & DNS

warn

26 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA iDNSSEC !Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: doug.ns.cloudflare.com: "2026.10.2"; harmony.ns.cloudflare.com: "2026.10.2". Hide or replace the version string.
    #17
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m39s), MX (2m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 2d and in the zone 1d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for optimizely.com ›

Mail

warn

29 passed 3 warn 0 failed

Areas

✓SPF ✓DMARC !DKIM ✓DNSSEC !MX !TLS ✓BIMI

Problems

  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: de-smtp-inbound-1.mimecast.com, de-smtp-inbound-2.mimecast.com
    #11
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: google (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • !
    Not configured
    TLS · MTA-STS is not configured, so other mail servers fall back to unencrypted delivery when TLS fails or is stripped by an attacker. Publish a _mta-sts TXT record and a policy at https://mta-sts.<domain>/.well-known/mta-sts.txt.
    #32

Recent checks

!

Full report

Mail report for optimizely.com ›