onsoranje.nl

Checked 21 October 2026, 21:24 UTC · via 8.8.8.8
✗Problems found
22 passed 3 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a:3169.submission.antispamcloud.com mx ip4:31.134.203.164 ip4:31.134.203.165 ip4:31.134.203.166 ip4:46.31.48.0/21 ip4:94.228.128.0/20 ip4:178.22.80.0/22 ip6:2a00:d00:ff:133::/64 ip6:2a00:d00:ff:129::/64 ip6:2a00:d01:ff:905::/64 ip6:2001:610:188:140::/64 ip4:167.89.0.0/17 ip4:208.117.48.0/20 ip4:50.31.32.0/19 ip4:198.37.144.0/20 ip4:198.21.0.0/21 ip4:192.254.112.0/20 ip4:168.245.0.0/17 ip4:149.72.0.0/16 ip4:159.183.0.0/16 ip4:223.165.113.0/24 ip4:223.165.115.0/24 ip4:223.165.118.0/23 ip4:223.165.120.0/23 ip4:83.98.176.0/24 ip4:83.98.168.240/28 ip4:82.94.175.64/26 ip4:149.210.146.83 ip4:149.210.146.85 ip4:149.210.144.235 ip4:149.210.144.182 ip4:178.63.60.209 ip4:83.98.176.152/30 include:sas.mail.e.sparkpost.com include:_netblocks.google.com include:_netblocks2.google.com include:_netblocks3.google.com ~all
DNS lookups
7 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=none; rua=mailto:lo4vm8wk@ag.eu.dmarcadvisor.com
Found at
_dmarc.onsoranje.nl
External report address
mailto:lo4vm8wk@ag.eu.dmarcadvisor.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:lo4vm8wk@ag.eu.dmarcadvisor.comAggregate report addresses

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:lo4vm8wk@ag.eu.dmarcadvisor.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

No keys found under the checked selectors

Found

Selectors
None found
_domainkey
NOERROR

Checks

  • !
    No key under common selectors
    The _domainkey name exists but no DKIM key was found under the common selectors. Selectors are provider-specific; check yours with -selector.
    #7

DNSSEC

pass

Signed, DS published at parent

Found

DNSKEY records
Yes (1)
DS at parent
Yes
Algorithms
RSASHA256 (8)
Key tags
34990
Signatures valid until
29 October 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-10-29 #21
    DNSKEY signatures are valid until 2026-10-29T00:00:00Z.

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mx.spamexperts.comA 154.59.104.23 AAAA 2001:978:2:2c::137:100fe2-r3-in.ams14.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓
20fallbackmx.spamexperts.euA 154.59.193.124 A 149.13.75.27 A 154.59.104.23 AAAA 2001:978:2:2c::137:100 AAAA 2001:978:2:6::f:124 AAAA 2001:978:2:7::162:100fe3-r3-in.du01.l.antispamcloud.com ✓ fe1-r3-in.fra02.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓ fe3-r3-in.du01.l.antispamcloud.com ✓ fe1-r3-in.fra02.l.antispamcloud.com ✓
30lastmx.spamexperts.netA 149.13.75.27 A 38.89.254.156 A 38.71.16.244 A 154.59.104.23 AAAA 2001:550:2:3::62:100 AAAA 2001:978:2:7::162:100 AAAA 2001:550:2:61::2fc:100 AAAA 2001:978:2:2c::137:100fe1-r3-in.fra02.l.antispamcloud.com ✓ fe1-r2-in.ch03.l.antispamcloud.com ✓ fe2-r2-in.la10.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓ fe2-r2-in.la10.l.antispamcloud.com ✓ fe1-r3-in.fra02.l.antispamcloud.com ✓ no PTR fe2-r3-in.ams14.l.antispamcloud.com ✓

Checks

  • ✓ 3 MX records #9
    Found 3 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.
  • ✓ Redundant MX hosts #12
    Found 3 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 3 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: 2001:550:2:61::2fc:100 (lastmx.spamexperts.net). Ask your hosting provider to set one.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx.spamexperts.comnone-
fallbackmx.spamexperts.eunone-
lastmx.spamexperts.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