live.com

Checked 22 October 2026, 09:40 UTC · via 8.8.8.8
✗Problems found
27 passed 3 warnings 1 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf-a.hotmail.com include:spf-b.hotmail.com include:spf-c.hotmail.com include:spf-d.hotmail.com include:spf.protection.outlook.com ~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

fail

p=none (_dmarc.live.com)

Found

Record
v=DMARC1; p=none; sp=quarantine; pct=100; rua=mailto:rua@dmarc.microsoft; ruf=mailto:ruf@dmarc.microsoft; fo=1
Found at
_dmarc.live.com
External report address
mailto:rua@dmarc.microsoft (authorized)
External report address
mailto:ruf@dmarc.microsoft (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
spquarantineSubdomain policy
pct100Percentage of mail the policy applies to
ruamailto:rua@dmarc.microsoftAggregate report addresses
rufmailto:ruf@dmarc.microsoftFailure report addresses
fo1Failure reporting options

Checks

  • ✗
    Policy: none (monitoring only)
    DMARC policy is set to 'none', which only monitors but doesn't protect against spoofing. Consider upgrading to 'quarantine' or ideally 'reject'.
    #4
  • ✓ Record published #5
    DMARC record exists for this domain.
  • ✓ Valid syntax #17
    DMARC record syntax is valid.
  • ✓ Aggregate reports enabled #19
    Aggregate reports are sent to: mailto:rua@dmarc.microsoft
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

pass

Selectors: selector1

Found

Selectors
selector1
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits

Checks

  • ✓ Keys found: selector1 #7
    DKIM keys found for this domain with selectors: selector1
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits.
  • ✓ No problematic flags #24
    No keys in test mode, revoked, or limited to SHA-1.

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
28654, 44331
Signatures valid until
1 December 2026, 14: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-12-01 #21
    DNSKEY signatures are valid until 2026-12-01T14:00:10Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
2live-com.olc.protection.outlook.comA 52.101.60.64 A 52.101.41.202 A 52.101.41.181 A 52.101.209.27no PTR no PTR no PTR no PTR

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: live-com.olc.protection.outlook.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.
  • !
    Addresses without reverse DNS
    These MX addresses have no PTR record, which many receivers treat as a spam signal: 52.101.60.64 (live-com.olc.protection.outlook.com), 52.101.41.202 (live-com.olc.protection.outlook.com), 52.101.41.181 (live-com.olc.protection.outlook.com), 52.101.209.27 (live-com.olc.protection.outlook.com). Ask your hosting provider to set one.
    #30

TLS

info

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

Found

MTA-STS record
v=STSv1; id=20190225000000Z;
Policy URL
https://mta-sts.live.com/.well-known/mta-sts.txt
Mode
enforce
Allowed MX
*.olc.protection.outlook.com
Max age
604800 seconds
TLS-RPT record
v=TLSRPTv1;rua=https://tlsrpt.azurewebsites.net/report

DANE (TLSA records)

MX hostTLSADNSSEC
live-com.olc.protection.outlook.comnone-

Checks

  • ✓ Record published #32
    MTA-STS record found with id 20190225000000Z.
  • ✓ Policy enforced #33
    The MTA-STS policy is enforced and cached for 168h0m0s.
  • ✓ All MX hosts covered #34
    Every MX host matches an mx: line of the MTA-STS policy.
  • ✓ Reports enabled #35
    TLS reports are sent to: https://tlsrpt.azurewebsites.net/report
  • 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