oosterhout.nl

Checked 22 October 2026, 15:02 UTC · via 8.8.8.8
!Passed with warnings
27 passed 5 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 include:_spf.equalit.nl include:spf.eprov.nl include:spf.signhost.com include:spf.flowmailer.net include:lms.plusport.com ip4:5.200.8.166 ip4:90.145.221.171 ip4:185.71.63.166 ip4:80.69.74.48 ip4:194.109.24.0/24 ip4:185.71.63.24 ip4:90.145.213.17 ip4:90.145.221.193 ip4:185.21.240.0/22 ip4:89.250.189.21 ip4:37.17.212.82 ip6:2a00:1fb8:a13:1::25 ip6:2001:4cb8:59c:1::25 ip4:194.53.72.4 ip4:194.53.72.252 ip4:31.223.173.49 ip4:45.80.232.20/30 ip4:85.90.85.193 ip4:85.90.85.177 ip4:176.74.239.242 ip4:213.208.232.101 ip6:2A07:CB84:3075:912:10:10:159:25 ip6:2A07:CB81:3711:815:10:10:160:25 -all
DNS lookups
9 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; ruf=mailto:dmarc_forensic@equalit.nl
Found at
_dmarc.oosterhout.nl
External report address
mailto:dmarc_forensic@equalit.nl (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
rufmailto:dmarc_forensic@equalit.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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.
  • ✓ 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
RSASHA512 (10)
Key tags
47975, 20091
Signatures valid until
20 November 2026, 15:42 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-20T15:42:16Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
5oosterhout-nl.y-v1.mx.microsoftA 52.101.181.156 A 52.101.185.21 A 52.101.68.29 A 52.101.68.25 AAAA 2a01:111:f403:ca48::12 AAAA 2a01:111:f403:ca48::e AAAA 2a01:111:f403:ca04::10 AAAA 2a01:111:f403:ca3c::8mail-wa4pr05cu00104.inbound.protection.outlook.com ✓ mail-zrxpr05cu00105.inbound.protection.outlook.com ✓ mail-dbapr03cu00105.inbound.protection.outlook.com ✓ mail-db8pr02cu00101.inbound.protection.outlook.com ✓ mail-miypr05cu00202.inbound.protection.outlook.com ✓ mail-miypr03cu00206.inbound.protection.outlook.com ✓ mail-dbapr03cu00100.inbound.protection.outlook.com ✓ mail-zrxpr05cu00100.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 1 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
oosterhout-nl.y-v1.mx.microsoft3 1 1 54883cc5f1849331… 3 1 1 cfd68bde4129c00a… 3 1 1 803f7447cc75b208… 2 0 1 ea7a25255d111fc3… 2 0 1 c1ad7778796d20bc…Yes

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
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • ✓ DANE on all MX hosts #36
    All 1 MX host publish DNSSEC-validated TLSA records.

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