sportfondsen.nl

Checked 22 October 2026, 16:11 UTC · via 8.8.8.8
!Passed with warnings
22 passed 6 warnings 0 failed 3 info

SPF

pass

SPF record published

Found

Record
v=spf1 a:static1.msdp1.com a:static2.msdp1.com ip4:46.182.222.130 ip4:46.182.222.133 ip4:46.182.222.142 ip4:91.192.38.98 ip4:46.182.222.151 ip4:193.37.205.73 ip4:185.224.89.95 ip4:213.126.50.252 ip4:178.237.39.1/28 ip4:178.237.39.145/28 ip4:94.103.156.226 ip4:148.251.193.188 ip4:212.72.62.129/27 ip4:77.73.225.208/29 ip4:178.237.40.116 ip4:185.46.182.1/24 ip4:20.82.87.96/28 ip4:185.20.209.82 ip4:77.94.242.7 ip4:31.186.226.160/27 ip4:185.20.211.0/25 ip4:185.172.199.0/25 ip4:91.103.152.0/24 ip6:2603:10a6:208:170::16 include:amazonses.com include:spf.protection.outlook.com include:spf.tribecrm.nl include:spf-breaks-email.bit.nl include:mailswitch.nl include:_spf_cd.spamtitan.com include:spf.zoho.eu ~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.sportfondsen.nl)

Found

Record
v=DMARC1; p=quarantine;
Found at
_dmarc.sportfondsen.nl
TagValueMeaning
vDMARC1Version
pquarantinePolicy

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.
  • !
    No aggregate reports (rua)
    DMARC record has no rua tag, so you receive no aggregate reports about who sends mail as your domain. Add rua=mailto:...
    #19
  • ✓ Subdomain policy: quarantine #20
    Subdomains are covered by policy 'quarantine'.

DKIM

pass

Selectors: selector1, selector2

Found

Selectors
selector1, selector2
_domainkey
NOERROR
SelectorKeyFlags
selector1RSA 2048 bits
selector2RSA 2048 bits

Checks

  • ✓ Keys found: selector1, selector2 #7
    DKIM keys found for this domain with selectors: selector1, selector2
  • ✓ Strong keys #23
    DKIM keys are strong enough: selector1: RSA 2048 bits; selector2: RSA 2048 bits.
  • ✓ 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

2 mail servers

Found

PriorityHostRecordsReverse DNS
10sportfondsen-mx1.titanhq.comA 35.158.242.254 A 35.158.11.197 A 3.125.67.59 A 3.70.162.203eu1-smtp2.titanhq.com (does not resolve back) eu1-smtp2.titanhq.com (does not resolve back) eu1-smtp1.titanhq.com (does not resolve back) eu1-smtp1.titanhq.com (does not resolve back)
20sportfondsen-mx2.titanhq.comA 3.70.162.203 A 35.158.11.197 A 3.125.67.59 A 35.158.242.254eu1-smtp1.titanhq.com (does not resolve back) eu1-smtp2.titanhq.com (does not resolve back) eu1-smtp1.titanhq.com (does not resolve back) eu1-smtp2.titanhq.com (does not resolve back)

Checks

  • ✓ 2 MX records #9
    Found 2 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: sportfondsen-mx1.titanhq.com, sportfondsen-mx2.titanhq.com
    #11
  • ✓ 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 does not match
    The PTR name of these addresses does not resolve back to the same address: 35.158.242.254 -> eu1-smtp2.titanhq.com, 35.158.11.197 -> eu1-smtp2.titanhq.com, 3.125.67.59 -> eu1-smtp1.titanhq.com, 3.70.162.203 -> eu1-smtp1.titanhq.com, 3.70.162.203 -> eu1-smtp1.titanhq.com, 35.158.11.197 -> eu1-smtp2.titanhq.com, 3.125.67.59 -> eu1-smtp1.titanhq.com, 35.158.242.254 -> eu1-smtp2.titanhq.com.
    #30

TLS

warn

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

Found

DANE (TLSA records)

MX hostTLSADNSSEC
sportfondsen-mx1.titanhq.comnone-
sportfondsen-mx2.titanhq.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