sparta-rotterdam.nl

Checked 22 October 2026, 16:10 UTC · via 8.8.8.8
✗Problems found
22 passed 5 warnings 2 failed 2 info

SPF

pass

SPF record published

Found

Record
v=spf1 mx include:spf.protection.outlook.com include:spf.bundeling.com include:spf.signhost.com include:_spf.exonet.nl include:_spf.transip.email ip4:136.144.214.176 ip4:185.131.228.0/25 ip4:185.131.228.128/25 ip4:185.131.229.0/25 ip4:185.64.33.133 ip4:185.64.35.133 ip4:213.144.242.0/28 ip4:89.146.30.0/27 ip4:213.144.234.160/27 ip4:46.44.162.254 ip4:89.146.1.51 ip4:89.146.1.52 ip4:89.146.1.63 ip4:46.44.142.238 ip4:89.146.1.57 ip4:89.146.63.164 ip6:2a02:22a0:0:1:2::2a ip6:2a02:22a0:0:1:2::2e ip6:2a02:22a0:0:2:2::12 ip6:2a02:22a0:0:1:2::2 ip6:2a02:22a0:0:1:2::5 ip6:2a02:22a0:0:2:2::5 -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

fail

p=none (_dmarc.sparta-rotterdam.nl)

Found

Record
v=DMARC1; p=none; rua=mailto:rua@dmarc.brevo.com
Found at
_dmarc.sparta-rotterdam.nl
External report address
mailto:rua@dmarc.brevo.com (authorized)
TagValueMeaning
vDMARC1Version
pnonePolicy
ruamailto:rua@dmarc.brevo.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:rua@dmarc.brevo.com
  • ✓ External report addresses authorized #29
    Report addresses in other domains have published their authorization.

DKIM

warn

Selectors: mail, s1, s2

Found

Selectors
mail, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 2048 bitsh=sha256
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

1 mail server

Found

PriorityHostRecordsReverse DNS
0spartarotterdam-nl01e.mail.protection.outlook.comA 52.101.209.28 A 52.101.209.31 A 52.101.91.21 A 52.101.73.153 AAAA 2a01:111:f403:ca04::9 AAAA 2a01:111:f403:ca04::d AAAA 2a01:111:f403:ca21::10 AAAA 2a01:111:f403:ca04::email-cpjpr05cu00104.inbound.protection.outlook.com ✓ mail-cpjpr05cu00207.inbound.protection.outlook.com ✓ mail-matpr05cu00105.inbound.protection.outlook.com ✓ mail-as8pr05cu00401.inbound.protection.outlook.com ✓ mail-db7pr03cu00601.inbound.protection.outlook.com ✓ mail-db6pr03cu00105.inbound.protection.outlook.com ✓ mail-matpr05cu00100.inbound.protection.outlook.com ✓ mail-db8pr02cu00106.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
spartarotterdam-nl01e.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

fail

https://www.sparta-rotterdam.nl/wp-content/themes/spartarotterdam/images/logos/sparta.svg

Found

Record
v=BIMI1;l=https://www.sparta-rotterdam.nl/wp-content/themes/spartarotterdam/images/logos/sparta.svg
Found at
default._bimi.sparta-rotterdam.nl
Logo
https://www.sparta-rotterdam.nl/wp-content/themes/spartarotterdam/images/logos/sparta.svg

Checks

  • !
    No certificate (a=)
    The logo is published without a Verified Mark Certificate. Gmail and Apple Mail only show BIMI logos with a VMC or CMC; Yahoo shows it without one.
    #38
  • ✗
    DMARC not strict enough for BIMI
    Mail clients will not show the logo. BIMI requires DMARC p=quarantine or p=reject (now p=none), a subdomain policy other than sp=none.
    #39