oad.nl

Checked 22 October 2026, 15:01 UTC · via 8.8.8.8
✗Problems found
25 passed 4 warnings 1 failed 3 info

SPF

fail

SPF record published

Found

Record
v=spf1 a mx include:spf.protection.outlook.com include:_spf.oad.nl ~all
DNS lookups
17 of 10
Void lookups
0 of 2

Checks

  • ✓ No deprecated ptr mechanism #1
    No ptr mechanism found in SPF record.
  • ✗
    17 DNS lookups, over the limit of 10
    SPF record needs 17 DNS lookups (including nested includes), more than the limit of 10. Receivers will return a permerror; reduce includes or flatten the record.
    #2
  • ✓ 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.oad.nl)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:administrator@oad.nl; ruf=mailto:administrator@oad.nl;
Found at
_dmarc.oad.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:administrator@oad.nlAggregate report addresses
rufmailto:administrator@oad.nlFailure report addresses

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:administrator@oad.nl
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ Report addresses in own domain #29
    All report addresses are in your own organizational domain.

DKIM

warn

Selectors: dkim, selector1, selector2, s1, s2

Found

Selectors
dkim, selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 1024 bitsh=sha256
selector1RSA 1024 bits
selector2RSA 1024 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: dkim, selector1, selector2, s1, s2 #7
    DKIM keys found for this domain with selectors: dkim, selector1, selector2, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: dkim (1024 bits), selector1 (1024 bits), selector2 (1024 bits), s2 (1024 bits). Rotate to a 2048-bit key.
    #23
  • ✓ 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 (1)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
146
Signatures valid until
5 November 2026, 00: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-05 #21
    DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

warn

2 mail servers

Found

PriorityHostRecordsReverse DNS
0oad-nl.mail.protection.outlook.comA 52.101.91.153 A 52.101.103.162 A 52.101.68.10 A 52.101.73.155 AAAA 2a01:111:f403:ca38::8 AAAA 2a01:111:f403:ca48::8 AAAA 2a01:111:f403:ca48::12 AAAA 2a01:111:f403:ca04::10mail-matpr04cu00101.inbound.protection.outlook.com ✓ mail-miypr03cu00202.inbound.protection.outlook.com ✓ mail-dbbpr03cu00102.inbound.protection.outlook.com ✓ mail-am7pr02cu00203.inbound.protection.outlook.com ✓ mail-wa4pr04cu00100.inbound.protection.outlook.com ✓ mail-miypr02cu00100.inbound.protection.outlook.com ✓ mail-miypr05cu00202.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓
500mx.sendgrid.netA 3.136.245.72 A 3.17.120.38 A 52.25.213.239 A 16.52.61.209 A 52.37.49.26 A 13.216.54.185 A 44.216.124.122 A 16.52.110.174 A 34.198.67.24 A 18.224.101.244 A 15.222.160.229 A 44.245.249.202ec2-3-136-245-72.us-east-2.compute.amazonaws.com ✓ ec2-3-17-120-38.us-east-2.compute.amazonaws.com ✓ ec2-52-25-213-239.us-west-2.compute.amazonaws.com ✓ ec2-16-52-61-209.ca-central-1.compute.amazonaws.com ✓ ec2-52-37-49-26.us-west-2.compute.amazonaws.com ✓ ec2-13-216-54-185.compute-1.amazonaws.com ✓ ec2-44-216-124-122.compute-1.amazonaws.com ✓ ec2-16-52-110-174.ca-central-1.compute.amazonaws.com ✓ ec2-34-198-67-24.compute-1.amazonaws.com ✓ ec2-18-224-101-244.us-east-2.compute.amazonaws.com ✓ ec2-15-222-160-229.ca-central-1.compute.amazonaws.com ✓ ec2-44-245-249-202.us-west-2.compute.amazonaws.com ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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: mx.sendgrid.net
    #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 20 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
oad-nl.mail.protection.outlook.comnone-
mx.sendgrid.netnone-

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