mojang.com

Checked 22 October 2026, 09:52 UTC · via 8.8.8.8
✗Problems found
23 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a mx include:spf.protection.outlook.com include:spf.mtasv.net include:_spf.google.com include:amazonses.com ~all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✓ 6 of 10 DNS lookups #2
    SPF record needs 6 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

warn

p=quarantine (_dmarc.mojang.com)

Found

Record
v=DMARC1; p=quarantine; pct=100; rua=mailto:re+mcad4hb0aan@dmarc.postmarkapp.com; sp=none; aspf=r;
Found at
_dmarc.mojang.com
External report address
mailto:re+mcad4hb0aan@dmarc.postmarkapp.com (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spnoneSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:re+mcad4hb0aan@dmarc.postmarkapp.comAggregate report addresses
aspfrSPF alignment (r = relaxed, s = strict)

Checks

  • !
    Policy: quarantine
    DMARC policy is set to 'quarantine'. Consider upgrading to 'reject' for stronger protection once you've verified legitimate emails are passing authentication.
    #4
  • ✓ 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:re+mcad4hb0aan@dmarc.postmarkapp.com
  • !
    Subdomains unprotected (sp=none)
    DMARC subdomain policy is sp=none, so spoofed mail from subdomains is not blocked. Consider sp=quarantine or sp=reject.
    #20
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

fail

Selectors: google, pm

Found

Selectors
google, pm
_domainkey
NOERROR
SelectorKeyFlags
googleRSA 1024 bits
pmRSA 768 bits

Checks

  • ✓ Keys found: google, pm #7
    DKIM keys found for this domain with selectors: google, pm
  • ✗
    Weak DKIM key
    RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): pm (768 bits). Rotate to a 2048-bit key.
    #23
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0microsoft-com.mail.protection.outlook.comA 52.101.60.191 A 52.101.41.125 A 52.101.10.12 A 52.101.9.4 AAAA 2a01:111:f403:c927::8 AAAA 2a01:111:f403:c902::2 AAAA 2a01:111:f403:f909::3 AAAA 2a01:111:f403:c95d::6mail-bn0pr05cu00107.inbound.protection.outlook.com ✓ mail-byapr05cu00605.inbound.protection.outlook.com ✓ mail-bn1pr21cu00204.inbound.protection.outlook.com ✓ mail-mn2pr05cu00304.inbound.protection.outlook.com ✓ mail-bn3pr0301cu00200.inbound.protection.outlook.com ✓ mail-sj0pr03cu01602.inbound.protection.outlook.com ✓ mail-bnypr03cu00103.inbound.protection.outlook.com ✓ mail-ph0pr02cu00106.inbound.protection.outlook.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.
  • ✓ All hosts have IPv6 #11
    All MX records resolve to IPv6 addresses.
  • !
    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 8 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
microsoft-com.mail.protection.outlook.comnone-

Checks

  • !
    Not configured
    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
  • i
    Not configured
    TLS-RPT lets senders report TLS delivery problems to you. It is most useful together with MTA-STS or DANE.
    #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

info

No BIMI record

Checks

  • i
    Not configured
    BIMI shows your logo next to your mail in supporting mail clients. It requires DMARC enforcement.
    #38