SurfaceMap › m › majestic.com

majestic.com

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

Domain & DNS

warn

30 passed 2 warn 0 failed

Areas

iRegistration iDelegation !Nameservers ✓SOA !DNSSEC ✓Records

Problems

  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.majesticseo.com: "9.11.36-RedHat-9.11.36-16.el8_10.2"; ns2.majesticseo.com: "9.11.4-P2-RedHat-9.11.4-26.P2.el7_9.16". Hide or replace the version string.
    #17
  • !
    NSEC3 with extra iterations or salt
    DNSSEC · NSEC3 uses 10 iterations and a 0-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Recent checks

!

Full report

Domain & DNS report for majestic.com ›

Mail

fail

28 passed 4 warn 1 failed

Areas

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

Problems

  • ✗
    Invalid TLS-RPT record
    TLS · Senders ignore the TLS-RPT record because of: 2 v=TLSRPTv1 records published; there must be exactly one.
    #35
  • !
    No key under common selectors
    DKIM · The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: mail.majestic.com
    #11
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    Policy in testing mode
    TLS · With mode: testing, senders only report TLS problems (via TLS-RPT) and still deliver without TLS. Switch to mode: enforce once reports are clean.
    #33

Recent checks

✗

Full report

Mail report for majestic.com ›