SurfaceMap › t › tijd.be

tijd.be

Checked 2026-10-22 07:12 UTC · first added 2026-10-21
!Passed with warnings Score 76 of 100

Domain & DNS

warn

19 passed 5 warn 0 failed

Areas

iRegistration !Delegation !Nameservers !SOA !DNSSEC !Records

Problems

  • !
    NS sets differ
    Delegation · The nameservers at the parent and in the zone should be the same. Only in the zone: a9-66.akam.net. a1-190.akam.net, a13-66.akam.net, a14-67.akam.net, a28-64.akam.net, a6-65.akam.net, a9-66.akam.net report NS a1-190.akam.net a13-66.akam.net a14-67.akam.net a28-64.akam.net a6-65.akam.net a9-66.akam.net.
    #7
  • !
    Software version disclosed
    Nameservers · These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: a1-190.akam.net: "41824.6"; a1-190.akam.net: "41824.9"; a13-66.akam.net: "41824.8"; a13-66.akam.net: "41824.7"; a14-67.akam.net: "48878.33"; a14-67.akam.net: "48878.31"; a28-64.akam.net: "48878.31"; a28-64.akam.net: "48878.32"; a6-65.akam.net: "48878.31"; a6-65.akam.net: "48878.29"; a9-66.akam.net: "41824.10"; a9-66.akam.net: "41824.6". Hide or replace the version string.
    #17
  • !
    Unusual SOA timers
    SOA · negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 1000h, negative TTL 2d.
    #23
  • !
    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
  • !
    Very low TTLs
    Records · These records have a TTL below 5m, causing extra queries and slower lookups: A (20s), AAAA (20s). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 2d; resolvers may use either.
    #32

Recent checks

!

Full report

Domain & DNS report for tijd.be ›

Mail

warn

26 passed 3 warn 0 failed

Areas

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

Problems

  • !
    Not enabled
    DNSSEC · DNSSEC is not enabled for this domain. Consider enabling DNSSEC to protect against DNS spoofing attacks.
    #8
  • !
    Single MX host, no backup
    MX · Only one MX record found. For better email reliability, consider adding at least one backup MX server.
    #12
  • !
    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 tijd.be ›