ranzijn.nl

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

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:84.246.15.63 include:trustpilotservice.com include:sendgrid.net include:spf.protection.outlook.com include:spf.animana.com include:amazonses.com ip4:46.31.48.0/21 ip4:5.100.226.177/28 ip4:185.46.182.1 ip4:185.46.182.200/29 ip4:185.46.182.208/31 include:_spf.yellowyard.nl -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.ranzijn.nl)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@ranzijn.nl;
Found at
_dmarc.ranzijn.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@ranzijn.nlAggregate 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:dmarc@ranzijn.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

fail

Selectors: dkim, selector1, selector2, s1

Found

Selectors
dkim, selector1, selector2, s1
_domainkey
NOERROR
SelectorKeyFlags
dkimRSA 384 bits
selector1RSA 1024 bits
selector2RSA 1024 bits
s1RSA 2048 bits

Checks

  • ✓ Keys found: dkim, selector1, selector2, s1 #7
    DKIM keys found for this domain with selectors: dkim, selector1, selector2, s1
  • ✗
    Weak DKIM key
    RSA keys shorter than 1024 bits can be cracked and are ignored by receivers (RFC 8301): dkim (384 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
2371, 34505
Signatures valid until
13 December 2026, 17:57 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-13 #21
    DNSKEY signatures are valid until 2026-12-13T17:57:23Z.

MX

warn

1 mail server

Found

PriorityHostRecordsReverse DNS
0ranzijn-nl.mail.protection.outlook.comA 52.101.185.114 A 52.101.68.27 A 52.101.68.21 A 52.101.209.153 AAAA 2a01:111:f403:ca04::f AAAA 2a01:111:f403:ca04::e AAAA 2a01:111:f403:ca09::28 AAAA 2a01:111:f403:ca21::10mail-zrxpr04cu00102.inbound.protection.outlook.com ✓ mail-db7pr03cu00503.inbound.protection.outlook.com ✓ mail-db4pr02cu00205.inbound.protection.outlook.com ✓ mail-cpjpr04cu00101.inbound.protection.outlook.com ✓ mail-db7pr03cu00507.inbound.protection.outlook.com ✓ mail-db8pr02cu00106.inbound.protection.outlook.com ✓ mail-am6pr02cu00300.inbound.protection.outlook.com ✓ mail-matpr05cu00100.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 0 of 1 MX hosts

Found

DANE (TLSA records)

MX hostTLSADNSSEC
ranzijn-nl.mail.protection.outlook.comnone-

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