lapperre.be

16 of 16 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 16 nameserver addresses answered.
• ✓ All authoritative #15

  Every responding nameserver answers authoritatively for the zone.
• ✓ No recursion #16

  The nameservers do not answer recursive queries for other domains.
• !

  Software version disclosed

  These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns4-09.azure-dns.info: "Knot DNS 3.1.2.1770717641.d6b376aff". Hide or replace the version string.

  #17
• ✓ Zone transfers refused #18

  No nameserver allows a zone transfer to the public.
• ✓ TCP supported #19

  All nameservers answer over TCP.
• ✓ EDNS supported #20

  All nameservers support EDNS(0).
• ✓ Public addresses #21

  All nameserver addresses are publicly routable.

serial 1 · primary ns-381.awsdns-47.com

Found

Primary (MNAME)

ns-381.awsdns-47.com

Contact (RNAME)

awsdns-hostmaster.amazon.com

Serial

1

Refresh / retry

86400 s / 7200 s

Expire

3600000 s

Negative TTL

172800 s

Serial per nameserver

Checks

• !

  Serials differ

  The nameservers serve different versions of the zone: 1 on ns-1188.awsdns-20.org (205.251.196.164), ns-1188.awsdns-20.org (2600:9000:5304:a400::1), ns-1786.awsdns-31.co.uk (205.251.198.250), ns-1786.awsdns-31.co.uk (2600:9000:5306:fa00::1), ns-381.awsdns-47.com (205.251.193.125), ns-381.awsdns-47.com (2600:9000:5301:7d00::1), ns-772.awsdns-32.net (205.251.195.4), ns-772.awsdns-32.net (2600:9000:5303:400::1); 2021040716 on ns1-09.azure-dns.com (13.107.236.9), ns1-09.azure-dns.com (2603:1061:0:700::9), ns2-09.azure-dns.net (150.171.21.9), ns2-09.azure-dns.net (2620:1ec:8ec:700::9), ns3-09.azure-dns.org (204.14.183.9), ns3-09.azure-dns.org (2a01:111:4000:700::9), ns4-09.azure-dns.info (208.84.5.9), ns4-09.azure-dns.info (2620:1ec:bda:700::9). This is normal for a few minutes after a change; if it lasts, zone transfers to the secondaries are failing.

  #22
• !

  Unusual SOA timers

  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
• ✓ Primary is a public nameserver #24

  The primary nameserver ns-381.awsdns-47.com is one of the listed nameservers.
• ✓ Contact awsdns-hostmaster@amazon.com #25

  The SOA RNAME awsdns-hostmaster.amazon.com means awsdns-hostmaster@amazon.com.
• ✓ Counter serial #26

  The serial 1 is a plain counter.

Not signed

Found

Validated by resolver

no

Checks

• !

  Not signed

  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

21 records at the apex

Found

Read from

205.251.196.164:53

Checks

• !

  Very low TTLs

  These records have a TTL below 5m, causing extra queries and slower lookups: A (1m). 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
• ✓ No CNAME at the apex #33

  The zone apex has no CNAME record.
• ✓ No wildcard #34

  Names that don't exist return NXDOMAIN.
• i

  No CAA records

  Without CAA records any certificate authority may issue certificates for this domain. A CAA record limits issuance to the CAs you use.

  #35