securityaffairs.com

Checked 22 October 2026, 10:35 UTC · via 8.8.8.8
✗Problems found
15 passed 4 warnings 2 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:spf.protection.outlook.com -all
DNS lookups
1 of 10
Void lookups
0 of 2

Checks

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

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

fail

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NXDOMAIN

Checks

  • ✗
    No DKIM keys published
    _domainkey.securityaffairs.com does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7

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

2 mail servers

Found

PriorityHostRecordsReverse DNS
0securityaffairs-com.mail.protection.outlook.comA 52.101.10.5 A 52.101.41.201 A 52.101.41.58 A 52.101.40.53 AAAA 2a01:111:f403:c902::5 AAAA 2a01:111:f403:f909:: AAAA 2a01:111:f403:c902::14 AAAA 2a01:111:f403:c95d::4mail-bn6pr04cu00105.inbound.protection.outlook.com ✓ mail-byapr03cu00201.inbound.protection.outlook.com ✓ mail-sj0pr02cu00102.inbound.protection.outlook.com ✓ mail-cy3pr05cu00205.inbound.protection.outlook.com ✓ mail-sj2pr05cu00505.inbound.protection.outlook.com ✓ mail-bn6pr04cu00200.inbound.protection.outlook.com ✓ mail-byapr04cu00204.inbound.protection.outlook.com ✓ mail-ph6pr04cu00104.inbound.protection.outlook.com ✓
32767ms93724931.msv1.invalid(does not resolve)

Checks

  • ✓ 2 MX records #9
    Found 2 MX records for this domain.
  • !
    Hosts without IP addresses
    The following MX hosts could not be resolved to IP addresses: ms93724931.msv1.invalid
    #10
  • !
    Hosts without IPv6
    The following MX hosts could not be resolved to IPv6 addresses: ms93724931.msv1.invalid
    #11
  • ✓ Redundant MX hosts #12
    Found 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 2 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
securityaffairs-com.mail.protection.outlook.comnone-
ms93724931.msv1.invalidnone-

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