SurfaceMap › i › interforcecms.nl

interforcecms.nl

Checked 2026-10-22 13:52 UTC · first added 2026-10-21
✗Problems found Score 42 of 100

Domain & DNS

fail

23 passed 2 warn 1 failed

Areas

iRegistration !Delegation ✗Nameservers ✓SOA !DNSSEC iRecords

Problems

  • ✗
    No DNS over TCP
    Nameservers · DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns03.interforce-dns.nl (2a01:7c8:bb01:2d7::2): dial tcp [2a01:7c8:bb01:2d7::2]:53: connect: no route to host.
    #19
  • !
    Glue differs from the zone
    Delegation · The addresses at the parent (glue) differ from the addresses in the zone: ns01.inter-hosting.nl (glue 178.255.24.11, zone 178.255.24.11, 2a13:4541:0:2102::3); ns02.inter-hosting.nl (glue 178.255.24.12, zone 178.255.24.12, 2a13:4541:0:2102::4); ns03.interforce-dns.nl (glue 84.247.10.127, zone 84.247.10.127, 2a01:7c8:bb01:2d7::2). Update the glue at your registrar.
    #8
  • !
    Not signed
    DNSSEC · The zone is not signed with DNSSEC, so answers can be spoofed. Enable DNSSEC at your DNS provider and publish the DS record at your registrar.
    #27

Recent checks

✗

Full report

Domain & DNS report for interforcecms.nl ›

Mail

fail

7 passed 4 warn 3 failed

Areas

✗SPF ✗DMARC ✗DKIM !DNSSEC !MX !TLS iBIMI

Problems

  • ✗
    No DMARC record
    DMARC · 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
  • ✗
    No SPF record
    SPF · No SPF record was found for this domain. SPF is important for preventing email spoofing. Add an SPF record to specify which servers are authorized to send email for your domain.
    #6
  • ✗
    No DKIM keys published
    DKIM · _domainkey.interforcecms.nl does not exist (NXDOMAIN), so no DKIM keys are published. DKIM helps prevent email spoofing. Configure DKIM with your email service provider.
    #7
  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Hosts without IPv6
    MX · The following MX hosts could not be resolved to IPv6 addresses: eu1-smtp-mx1.titanhq.com, eu1-smtp-mx2.titanhq.com
    #11
  • !
    Reverse DNS does not match
    MX · 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.125.67.59 -> eu1-smtp1.titanhq.com, 35.158.242.254 -> eu1-smtp2.titanhq.com, 35.158.11.197 -> eu1-smtp2.titanhq.com, 3.70.162.203 -> eu1-smtp1.titanhq.com.
    #30
  • !
    Not configured
    TLS · 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

Recent checks

✗

Full report

Mail report for interforcecms.nl ›