ladbrokes.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

dns1.itsfogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.com

Found

Parent zone

be

Delegation from

a.nsset.be (194.0.6.1)

NS at the parent

dns1.itsfogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.com

NS in the zone

dns1.itsfogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.com

Checks

• ✓ 6 nameservers #6

  Delegated to dns1.itsfogo.com, dns2.itsfogo.com, dns3.itsfogo.com, dns4.itsfogo.com, dns5.itsfogo.com, dns6.itsfogo.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 6 IPv4 /24s and 6 IPv6 /48s.
• i

  All nameservers in one AS

  All nameserver addresses are announced by one network operator (AS12008 (VERCARA - Vercara, LLC, US): 12 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.

12 of 12 addresses answer authoritatively

Found

Checks

• ✓ All respond #14

  All 12 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: dns1.itsfogo.com: "UltraDNS Nameserver"; dns2.itsfogo.com: "UltraDNS Nameserver"; dns3.itsfogo.com: "UltraDNS Nameserver"; dns4.itsfogo.com: "UltraDNS Nameserver"; dns5.itsfogo.com: "UltraDNS Nameserver"; dns6.itsfogo.com: "UltraDNS Nameserver".

  #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.

19 records at the apex

Found

Read from

156.154.64.14:53

Checks

• ✓ TTLs within range #32

  TTLs: A 5m, MX 1h, NS 1d.
• ✓ 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