watertaxirotterdam.nl

Checked 22 October 2026, 17:11 UTC · via 8.8.8.8
✗Problems found
17 passed 5 warnings 1 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx a a:mx.watertaxirotterdam.nl mx:mailer.twinfield.com include:sendgrid.net ~all
DNS lookups
6 of 10
Void lookups
0 of 2

Checks

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

No DMARC record found

Checks

  • ✗
    No DMARC record
    No DMARC record was found for this domain. DMARC is essential for preventing email spoofing. Add a DMARC record with p=reject or at least p=quarantine.
    #5

DKIM

warn

Selectors: mail, s1, s2

Found

Selectors
mail, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bits
s1RSA 2048 bits
s2RSA 1024 bits

Checks

  • ✓ Keys found: mail, s1, s2 #7
    DKIM keys found for this domain with selectors: mail, s1, s2
  • !
    1024-bit DKIM key
    1024-bit RSA keys are the minimum and are considered weak today: 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

warn

Not signed

Found

DNSKEY records
No (0)
DS at parent
No

Checks

  • !
    Not enabled
    DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8

MX

warn

3 mail servers

Found

PriorityHostRecordsReverse DNS
10mx1.maddogs.nlCNAME mx.spamexperts.com A 154.59.104.23 AAAA 2001:978:2:2c::137:100fe2-r3-in.ams14.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓
20mx2.maddogs.nlCNAME fallbackmx.spamexperts.eu A 149.13.75.27 A 154.59.193.124 A 154.59.104.23 AAAA 2001:978:2:7::162:100 AAAA 2001:978:2:6::f:124 AAAA 2001:978:2:2c::137:100fe1-r3-in.fra02.l.antispamcloud.com ✓ fe3-r3-in.du01.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓ fe1-r3-in.fra02.l.antispamcloud.com ✓ fe3-r3-in.du01.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓
30mx3.maddogs.nlCNAME lastmx.spamexperts.net A 38.89.254.156 A 149.13.75.27 A 154.59.104.23 A 38.71.16.244 AAAA 2001:550:2:3::62:100 AAAA 2001:978:2:2c::137:100 AAAA 2001:550:2:61::2fc:100 AAAA 2001:978:2:7::162:100fe1-r2-in.ch03.l.antispamcloud.com ✓ fe1-r3-in.fra02.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓ fe2-r2-in.la10.l.antispamcloud.com ✓ fe2-r2-in.la10.l.antispamcloud.com ✓ fe2-r3-in.ams14.l.antispamcloud.com ✓ no PTR fe1-r3-in.fra02.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.
  • !
    Hosts are CNAMEs
    MX records must point to a host name with A/AAAA records, not to a CNAME: mx1.maddogs.nl -> mx.spamexperts.com, mx2.maddogs.nl -> fallbackmx.spamexperts.eu, mx3.maddogs.nl -> lastmx.spamexperts.net
    #22
  • !
    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 (mx3.maddogs.nl). 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
mx1.maddogs.nlnone-
mx2.maddogs.nlnone-
mx3.maddogs.nlnone-

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