optisport.nl

Checked 22 October 2026, 15:02 UTC · via 8.8.8.8
!Passed with warnings
27 passed 5 warnings 0 failed 1 info

SPF

pass

SPF record published

Found

Record
v=spf1 ip4:5.172.45.6 ip4:193.37.205.73 ip4:46.182.222.142 ip4:91.192.38.98 ip4:178.255.193.244 ip4:46.182.222.130 ip4:46.182.222.133 ip4:149.72.114.169 ip4:212.72.62.129/27 ip4:80.246.186.181 include:spf.afas.online include:_spf.spam-filter.email include:spf.mailjet.com include:spf.icontroller.eu include:spf.dewi-online.nl include:autotask.net include:spf.flowmailer.net include:spf.protection.outlook.com -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.optisport.nl)

Found

Record
v=DMARC1; p=quarantine; rua=mailto:dmarc@optisport.nl; fo=1;
Found at
_dmarc.optisport.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy
ruamailto:dmarc@optisport.nlAggregate report addresses
fo1Failure reporting options

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@optisport.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

warn

Selectors: mail, selector1, selector2, s1, s2

Found

Selectors
mail, selector1, selector2, s1, s2
_domainkey
NOERROR
SelectorKeyFlags
mailRSA 1024 bits
selector1RSA 1024 bits
selector2RSA 1024 bits
s1RSA 2048 bits
s2RSA 2048 bits

Checks

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

Signed, but no DS at parent

Found

DNSKEY records
Yes (1)
DS at parent
No
Algorithms
ECDSAP256SHA256 (13)
Key tags
37509
Signatures valid until
5 November 2026, 00:00 UTC

Checks

  • !
    Signed, but no DS at parent
    The zone is signed (DNSKEY present) but the parent has no DS record, so the chain of trust is incomplete. Publish the DS record at your registrar.
    #8
  • ✓ Signatures valid until 2026-11-05 #21
    DNSKEY signatures are valid until 2026-11-05T00:00:00Z.

MX

pass

2 mail servers

Found

PriorityHostRecordsReverse DNS
10mx.spam-filter.emailA 217.18.68.80 A 178.255.197.80 A 178.255.194.80 A 178.255.194.180 AAAA 2a00:19c0:a074:80::1 AAAA 2a00:19c0:c198:80::1 AAAA 2a00:19c0:c197:180::1 AAAA 2a00:19c0:a064:80::1mx02.spam-filter.email ✓ mx08.spam-filter.email ✓ mx06.spam-filter.email ✓ mx10.spam-filter.email ✓ mx04.spam-filter.email ✓ mx09.spam-filter.email ✓ mx11.spam-filter.email ✓ mx01.spam-filter.email ✓
20fallbackmx.spam-filter.cloudA 178.255.198.180 A 185.214.149.80 A 217.18.77.80 A 217.18.68.80 AAAA 2a00:19c0:c197:80::1 AAAA 2a00:19c0:c197:180::1 AAAA 2a00:19c0:a064:80::1 AAAA 2a00:19c0:a074:80::1mx12.spam-filter.email ✓ mx03.spam-filter.email ✓ mx05.spam-filter.email ✓ mx02.spam-filter.email ✓ mx08.spam-filter.email ✓ mx11.spam-filter.email ✓ mx01.spam-filter.email ✓ mx04.spam-filter.email ✓

Checks

  • ✓ 2 MX records #9
    Found 2 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 2 MX records, which provides redundancy for email delivery.
  • ✓ At most 5 MX records #13
    Found 2 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 16 MX addresss have a PTR record that resolves back to them.

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
mx.spam-filter.email3 1 1 566a94b9534c5001…Yes
fallbackmx.spam-filter.cloud3 1 1 566a94b9534c5001…Yes

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
  • !
    Not configured
    MTA-STS or DANE is used without TLS-RPT, so you get no reports when senders fail to deliver because of TLS problems. Publish _smtp._tls TXT "v=TLSRPTv1; rua=mailto:...".
    #35
  • ✓ DANE on all MX hosts #36
    All 2 MX hosts publish DNSSEC-validated TLSA records.

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