schunck.nl

Checked 22 October 2026, 15:50 UTC · via 8.8.8.8
!Passed with warnings
25 passed 5 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx include:mailing.ticketteam.cloud include:spf.afas.online include:spf.topdesk.net include:eu.zcsend.net include:spf.protection.outlook.com include:oclcspf3.oclc.org include:_spf.mail.services.bastion365.net ip4:108.61.221.71 ip4:144.178.242.2 ip4:93.95.251.150 -all
DNS lookups
10 of 10
Void lookups
0 of 2

Checks

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

Found

Record
v=DMARC1; p=quarantine; sp=quarantine; rua=mailto:watchdog2@watchdog.kevlarr.io; adkim=r; aspf=r;
Found at
_dmarc.schunck.nl
External report address
mailto:watchdog2@watchdog.kevlarr.io (authorized)
TagValueMeaning
vDMARC1Version
pquarantinePolicy
spquarantineSubdomain policy
ruamailto:watchdog2@watchdog.kevlarr.ioAggregate report addresses
adkimrDKIM alignment (r = relaxed, s = strict)
aspfrSPF alignment (r = relaxed, s = strict)

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:watchdog2@watchdog.kevlarr.io
  • ✓ 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

warn

Selectors: selector1, s1, s2

Found

Selectors
selector1, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, s1, s2 #7
    DKIM keys found for this domain with selectors: selector1, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: selector1 (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 (2)
DS at parent
Yes
Algorithms
ECDSAP256SHA256 (13)
Key tags
34505, 2371
Signatures valid until
12 December 2026, 13:46 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-12 #21
    DNSKEY signatures are valid until 2026-12-12T13:46:23Z.

MX

warn

4 mail servers

Found

PriorityHostRecordsReverse DNS
0schunck-nl.mail.protection.outlook.comA 52.101.91.159 A 52.101.73.145 A 52.101.103.143 A 52.101.185.114 AAAA 2a01:111:f403:ca09::20 AAAA 2a01:111:f403:ca48::c AAAA 2a01:111:f403:ca48::12 AAAA 2a01:111:f403:c967::8mail-matpr04cu00207.inbound.protection.outlook.com ✓ mail-am6pr02cu00301.inbound.protection.outlook.com ✓ mail-miypr03cu00107.inbound.protection.outlook.com ✓ mail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-as8pr05cu00400.inbound.protection.outlook.com ✓ mail-miypr03cu00104.inbound.protection.outlook.com ✓ mail-miypr05cu00202.inbound.protection.outlook.com ✓ mail-cpjpr04cu00100.inbound.protection.outlook.com ✓
10mx.zoho.euA 185.230.214.166 A 185.230.212.166mx2.zoho.eu ✓ mx.zoho.eu ✓
20mx2.zoho.euA 185.230.214.166mx2.zoho.eu ✓
50mx3.zoho.euA 185.230.212.166mx2.zoho.eu (does not resolve back)

Checks

  • ✓ 4 MX records #9
    Found 4 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.zoho.eu, mx2.zoho.eu, mx3.zoho.eu
    #11
  • ✓ Redundant MX hosts #12
    Found 4 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 4 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 does not match
    The PTR name of these addresses does not resolve back to the same address: 185.230.212.166 -> mx2.zoho.eu.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
schunck-nl.mail.protection.outlook.comnone-
mx.zoho.eunone-
mx2.zoho.eunone-
mx3.zoho.eunone-

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