redlights.be

Checked 22 October 2026, 07:02 UTC · via 8.8.8.8
!Passed with warnings
25 passed 2 warnings 0 failed 6 info

Registration

info

.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

Delegation

info

ns-cloud1.googledomains.com, ns-cloud2.googledomains.com, ns-cloud3.googledomains.com, ns-cloud4.googledomains.com

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
ns-cloud1.googledomains.com, ns-cloud2.googledomains.com, ns-cloud3.googledomains.com, ns-cloud4.googledomains.com
NS in the zone
ns-cloud1.googledomains.com, ns-cloud2.googledomains.com, ns-cloud3.googledomains.com, ns-cloud4.googledomains.com
NameserverAddressesNetwork (AS)Glue
ns-cloud1.googledomains.com216.239.32.106 2001:4860:4802:32::6aAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud2.googledomains.com216.239.34.106 2001:4860:4802:34::6aAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud3.googledomains.com216.239.36.106 2001:4860:4802:36::6aAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-
ns-cloud4.googledomains.com216.239.38.106 2001:4860:4802:38::6aAS15169 GOOGLE - Google LLC, US AS15169 GOOGLE - Google LLC, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns-cloud1.googledomains.com, ns-cloud2.googledomains.com, ns-cloud3.googledomains.com, ns-cloud4.googledomains.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.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:4860:4802::/48, while the other address family is spread over several networks.
    #10
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS15169 (GOOGLE - Google LLC, 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.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns-cloud1.googledomains.com 216.239.32.106NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-cloud1.googledomains.com 2001:4860:4802:32::6aNOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-cloud2.googledomains.com 216.239.34.106NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-cloud2.googledomains.com 2001:4860:4802:34::6aNOERROR, 12 ms, authoritativenoyes / yesrefused-
ns-cloud3.googledomains.com 216.239.36.106NOERROR, 42 ms, authoritativenoyes / yesrefused-
ns-cloud3.googledomains.com 2001:4860:4802:36::6aNOERROR, 42 ms, authoritativenoyes / yesrefused-
ns-cloud4.googledomains.com 216.239.38.106NOERROR, 11 ms, authoritativenoyes / yesrefused-
ns-cloud4.googledomains.com 2001:4860:4802:38::6aNOERROR, 11 ms, authoritativenoyes / yesrefused-

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.
  • ✓ No version disclosed #17
    The nameservers don't reveal their software version.
  • ✓ 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.

SOA

warn

serial 2033759610 · primary ns-cloud1.googledomains.com

Found

Primary (MNAME)
ns-cloud1.googledomains.com
Contact (RNAME)
root.redlights.be
Serial
2033759610
Refresh / retry
7200 s / 3600 s
Expire
86400 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns-cloud1.googledomains.com (216.239.32.106)2033759610
ns-cloud1.googledomains.com (2001:4860:4802:32::6a)2033759610
ns-cloud2.googledomains.com (216.239.34.106)2033759610
ns-cloud2.googledomains.com (2001:4860:4802:34::6a)2033759610
ns-cloud3.googledomains.com (216.239.36.106)2033759610
ns-cloud3.googledomains.com (2001:4860:4802:36::6a)2033759610
ns-cloud4.googledomains.com (216.239.38.106)2033759610
ns-cloud4.googledomains.com (2001:4860:4802:38::6a)2033759610

Checks

  • ✓ Serial 2033759610 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    expire 1d is shorter than 7d; secondaries stop answering too soon when the primary is down. Current values: refresh 2h, retry 1h, expire 1d, negative TTL 1h.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns-cloud1.googledomains.com is one of the listed nameservers.
  • ✓ Contact root@redlights.be #25
    The SOA RNAME root.redlights.be means root@redlights.be.
  • ✓ Timestamp serial #26
    The serial 2033759610 is a Unix timestamp (2034-06-12 21:13 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
1 iterations, 8-byte salt
Signatures valid until
11 November 2026

DS at the parent

Key tagAlgorithmDigestMatches a key
15380RSASHA256 (8)SHA256 D2A18108CCA4811E…yes

DNSKEY in the zone

Key tagRoleAlgorithm
15380KSK (257)RSASHA256 (8)
65115ZSK (256)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 15380 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2026-11-11 #30
    The earliest DNSKEY/SOA signature expires at 2026-11-11 10:01 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 1 iteration and a 8-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

info

19 records at the apex

Found

Read from
216.239.32.106:53
TypeValueTTL
SOAns-cloud1.googledomains.com. root.redlights.be. 2033759610 7200 3600 86400 36003600
NSns-cloud4.googledomains.com.21600
NSns-cloud3.googledomains.com.21600
NSns-cloud1.googledomains.com.21600
NSns-cloud2.googledomains.com.21600
A34.107.190.893600
AAAA2600:1901:0:cfb1::3600
MX0 redlights-be.mail.protection.outlook.com.3600
TXT"MS=ms91236777"3600
TXT"_ysjdqxqh9vma4wgr47bfyjz0wv9tsty"3600
TXT"google-site-verification=U-9eBPiTXdfCdNEGfwnv7pek0JvHk3DtcNHLsornttk"3600
TXT"google-site-verification=-xO2Z7DiPfiGFTnq7q_ObaVEn_kHOM3iTLjRoz5m90w"3600
TXT"v=spf1 ip4:83.217.72.40 ip4:35.210.16.233 ip4:35.210.231.122 ip4:35.210.90.55 ip4:34.140.250.124 ip6:2a00:1c98:10:19::10 include:_spf.google.com include:spf.protection.outlook.com include:email.freshdesk.com ~all"3600
TXT"MS=ms13840325"3600
TXT"piano mauve whiskey"3600
CAA0 issue "letsencrypt.org"300
CAA0 issuewild "digicert.com"300
CAA0 issue "digicert.com"300
CAA0 issuewild "letsencrypt.org"300

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, AAAA 1h, MX 1h, NS 6h. The NS TTL at the parent is 1d and in the zone 6h; 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
  • ✓ CAA restricts issuance #35
    Certificates may be issued by: letsencrypt.org, digicert.com.