talixo.be

.be country-code

Found

TLD

.be (country-code)

ICANN policies apply

no

Checks

• i

  .be is a country-code TLD (ccTLD)

  Country-code TLD: governed by its local registry under national policy, not by an ICANN contract. Registrar accreditation, dispute resolution and RDAP/WHOIS rules are set by the registry.

  #1
• ✓ TLD delegated and signed #2

  .be is delegated in the root zone and DNSSEC-signed.
• i

  Registration data not available

  No registration data via RDAP: the registry of .be offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.

  #3

ns1jlp.name.com, ns2lns.name.com, ns3sxz.name.com, ns4bty.name.com

Found

Parent zone

be

Delegation from

a.nsset.be (194.0.6.1)

NS at the parent

ns1jlp.name.com, ns2lns.name.com, ns3sxz.name.com, ns4bty.name.com

NS in the zone

ns1jlp.name.com, ns2lns.name.com, ns3sxz.name.com, ns4bty.name.com

Checks

• ✓ 4 nameservers #6

  Delegated to ns1jlp.name.com, ns2lns.name.com, ns3sxz.name.com, ns4bty.name.com.
• ✓ Parent and zone agree #7

  The parent delegation and the zone's NS records list the same nameservers.
• ✓ No glue needed #8

  All nameservers are outside the zone, so no glue records are needed.
• ✓ All names resolve #9

  Every nameserver name has an address and is not an alias.
• ✓ Nameservers in different networks #10

  The nameservers are spread over 2 IPv4 /24s and 2 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS62597 (NSONE - NSONE Inc, US): 8 addresses). An outage or attack on that network affects all nameservers; large anycast providers mitigate this, but a secondary DNS provider adds independence.

  #11
• i

  All nameserver names under .com

  All nameserver names are under one TLD, so a problem with that TLD also makes the nameservers unreachable. Some operators use names under two TLDs for extra resilience.

  #12
• ✓ All reachable over IPv6 #13

  Every nameserver has an IPv6 address.

8 of 8 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 8 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.
• i

  Identifying string disclosed

  These nameservers answer version queries with a string that is not a version number: ns1jlp.name.com: "19dd46e347df36b70933bf2be8023258586586a9"; ns2lns.name.com: "19dd46e347df36b70933bf2be8023258586586a9"; ns3sxz.name.com: "19dd46e347df36b70933bf2be8023258586586a9"; ns4bty.name.com: "19dd46e347df36b70933bf2be8023258586586a9".

  #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 1578958308 · primary ns1.name.com

Found

Primary (MNAME)

ns1.name.com

Contact (RNAME)

hostmaster.nsone.net

Serial

1578958308

Refresh / retry

7200 s / 3600 s

Expire

604800 s

Negative TTL

300 s

Serial per nameserver

Checks

• ✓ Serial 1578958308 everywhere #22

  All nameservers serve the same version of the zone.
• ✓ Timers within recommendations #23

  SOA refresh 2h, retry 1h, expire 7d, negative TTL 5m.
• i

  Hidden master

  The primary nameserver ns1.name.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.

  #24
• ✓ Contact hostmaster@nsone.net #25

  The SOA RNAME hostmaster.nsone.net means hostmaster@nsone.net.
• ✓ Timestamp serial #26

  The serial 1578958308 is a Unix timestamp (2020-01-13 23:31 UTC).

6 records at the apex

Found

Read from

163.114.216.17:53

Checks

• ✓ TTLs within range #32

  TTLs: A 5m, NS 5m. The NS TTL at the parent is 1d and in the zone 5m; resolvers may use either.
• ✓ No CNAME at the apex #33

  The zone apex has no CNAME record.
• i

  Wildcard record

  A random name under the zone resolves, so there is a wildcard (*) record. Typos and non-existent hosts resolve too, which can confuse mail and certificate checks.

  #34
• 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