majestic.com

Checked 22 October 2026, 09:42 UTC · via 8.8.8.8
✗Problems found
28 passed 4 warnings 1 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spfv4.majestic.com include:spfv6.majestic.com include:mail.zendesk.com a mx -all
DNS lookups
5 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 5 of 10 DNS lookups #2
    SPF record needs 5 DNS lookups (limit is 10).
  • ✓ Ends with -all #3
    SPF record properly uses -all to restrict unauthorized senders.
  • ✓ Record published #6
    SPF record exists for this domain.
  • ✓ Single record #16
    Exactly one SPF record is published.
  • ✓ Valid syntax #25
    All SPF mechanisms and modifiers are valid.
  • ✓ No void lookups #26
    All include/redirect targets exist.
  • ✓ No overly broad IP ranges #27
    All ip4/ip6 ranges are narrow enough.

DMARC

pass

p=reject (_dmarc.majestic.com)

Found

Record
v=DMARC1;p=reject;sp=reject;rua=mailto:dmarc@majestic.com;ruf=mailto:dmarc2@majestic.com;adkim=r;aspf=r;rf=afrf;fo=1;pct=100
Found at
_dmarc.majestic.com
TagValueMeaning
vDMARC1Version
prejectPolicy
sprejectSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:dmarc@majestic.comAggregate report addresses
rufmailto:dmarc2@majestic.comFailure report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)
fo1Failure reporting options
rfafrfFailure report format

Checks

  • ✓ Policy: reject #4
    DMARC policy is set to 'reject', which provides the strongest protection against email spoofing.
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Applies to 100% of mail #18
    DMARC policy applies to all failing mail.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:dmarc@majestic.com
  • ✓ Subdomain policy: reject #20
    Subdomains are covered by policy 'reject'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
39006, 41704
Signatures valid until
20 November 2026, 05:00 UTC

Checks

  • ✓ Signed, DS published at parent #8
    DNSSEC is enabled for this domain (DNSKEY and DS present), providing additional security for DNS lookups.
  • ✓ Signatures valid until 2026-11-20 #21
    DNSKEY signatures are valid until 2026-11-20T05:00:01Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
5mail.majestic.comA 188.64.34.186mail.majestic.com ✓

Checks

  • ✓ 1 MX record #9
    Found 1 MX records for this domain.
  • ✓ All hosts resolve #10
    All MX records resolve to valid IP addresses.
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: mail.majestic.com
    #11
  • !
    Single MX host, no backup
    Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • ✓ At most 5 MX records #13
    Found 1 MX records, which is within the recommended range (1-5).
  • ✓ No localhost targets #14
    No MX records pointing to localhost found.
  • ✓ No private IP addresses #15
    No MX records resolving to private IP addresses found.
  • ✓ No CNAME targets #22
    No MX records point to a CNAME.
  • ✓ Reverse DNS confirmed #30
    All 1 MX address have a PTR record that resolves back to them.

TLS

fail

MTA-STS testing · TLS-RPT · DANE on 0 of 1 MX hosts

Found

MTA-STS record
v=STSv1; id=2026061701
Policy URL
https://mta-sts.majestic.com/.well-known/mta-sts.txt
Mode
testing
Allowed MX
mail.majestic.com
Max age
86400 seconds
TLS-RPT record
v=TLSRPTv1;rua=mailto:dmarc@majestic.com

DANE (TLSA records)

MX hostTLSADNSSEC
mail.majestic.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 2026061701.
  • !
    Policy in testing mode
    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
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✗
    Invalid TLS-RPT record
    Senders ignore the TLS-RPT record because of: 2 v=TLSRPTv1 records published; there must be exactly one.
    #35
  • i
    Not used
    No MX host publishes TLSA records. DANE lets senders verify your mail server's certificate through DNSSEC; it requires DNSSEC on the MX host's zone.
    #36

BIMI

pass

https://majestic.com/bimiicon.svg

Found

Record
v=BIMI1; l=https://majestic.com/bimiicon.svg; a=https://majestic.com/bimiicon.pem; avp=brand;
Found at
default._bimi.majestic.com
Logo
https://majestic.com/bimiicon.svg
Certificate
https://majestic.com/bimiicon.pem

Checks

  • ✓ Logo and certificate published #38
    BIMI logo: https://majestic.com/bimiicon.svg; certificate: https://majestic.com/bimiicon.pem
  • ✓ DMARC meets BIMI requirements #39
    DMARC is enforced on all mail, as BIMI requires.