SurfaceMap › m › microstrategy.com

microstrategy.com

Checked 2026-10-22 09:51 UTC · first added 2026-10-21
✗Problems found Score 66 of 100

Domain & DNS

warn

29 passed 4 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA ✓DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only at the parent: a1-228.akam.net, a11-67.akam.net, a14-64.akam.net, a16-65.akam.net, a4-66.akam.net, a7-67.akam.net; only in the zone: a1-222.akam.net, a13-67.akam.net, a22-66.akam.net, a26-66.akam.net, a28-64.akam.net, a9-65.akam.net. a1-222.akam.net, a1-228.akam.net, a11-67.akam.net, a13-67.akam.net, a14-64.akam.net, a16-65.akam.net, a22-66.akam.net, a26-66.akam.net, a28-64.akam.net, a4-66.akam.net, a7-67.akam.net, a9-65.akam.net report NS a1-222.akam.net a13-67.akam.net a22-66.akam.net a26-66.akam.net a28-64.akam.net a9-65.akam.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-222.akam.net: "41824.4"; a1-222.akam.net: "41824.5"; a1-228.akam.net: "41824.10"; a1-228.akam.net: "41824.5"; a11-67.akam.net: "41824.5"; a11-67.akam.net: "41824.11"; a13-67.akam.net: "41824.5"; a13-67.akam.net: "41824.10"; a14-64.akam.net: "48878.30"; a14-64.akam.net: "48878.26"; a16-65.akam.net: "48878.29"; a16-65.akam.net: "48878.30"; a22-66.akam.net: "48878.32"; a22-66.akam.net: "48878.33"; a26-66.akam.net: "48878.26"; a26-66.akam.net: "48878.32"; a28-64.akam.net: "48878.31"; a28-64.akam.net: "48878.33"; a4-66.akam.net: "48878.29"; a4-66.akam.net: "48878.27"; a7-67.akam.net: "41824.4"; a7-67.akam.net: "41824.9"; a9-65.akam.net: "41824.5"; a9-65.akam.net: "41824.7". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · retry 1d should be shorter than refresh 1d; expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down; expire 1d must be longer than refresh + retry; negative caching TTL (minimum) 0s is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 1d, expire 1d, negative TTL 0s.
    #23
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). 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 microstrategy.com ›

Mail

fail

23 passed 4 warn 1 failed

Areas

✓SPF ✗DMARC !DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    Policy: none (monitoring only)
    DMARC · DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: us-smtp-inbound-1.mimecast.com, us-smtp-inbound-2.mimecast.com
    #11
  • !
    Signatures expire in 51h0m0s
    DNSSEC · DNSKEY signatures expire at 2026-10-24T12:26:45Z (in 51h0m0s). Check that re-signing works.
    #21
  • !
    1024-bit DKIM key
    DKIM · 1024-bit RSA keys are the minimum and are considered weak today: selector2 (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 microstrategy.com ›