verviers.be

Checked 22 October 2026, 07:21 UTC · via 8.8.8.8
!Passed with warnings
20 passed 3 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

warn

dns200.anycast.me, ns200.anycast.me

Found

Parent zone
be
Delegation from
a.nsset.be (194.0.6.1)
NS at the parent
dns200.anycast.me, ns200.anycast.me
NS in the zone
dns200.anycast.me, ns200.anycast.me
NameserverAddressesNetwork (AS)Glue
dns200.anycast.me46.105.206.200AS16276 OVH - OVH SAS, FR-
ns200.anycast.me46.105.207.200AS16276 OVH - OVH SAS, FR-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: dns200.anycast.me, ns200.anycast.me.
    #6
  • ✓ 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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS16276 (OVH - OVH SAS, FR): 2 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 .me
    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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
dns200.anycast.me 46.105.206.200NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns200.anycast.me 46.105.207.200NOERROR, 6 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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

pass

serial 2088166193 · primary dns200.anycast.me

Found

Primary (MNAME)
dns200.anycast.me
Contact (RNAME)
tech.ovh.net
Serial
2088166193
Refresh / retry
86400 s / 3600 s
Expire
3600000 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
dns200.anycast.me (46.105.206.200)2088166193
ns200.anycast.me (46.105.207.200)2088166193

Checks

  • ✓ Serial 2088166193 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 1d, retry 1h, expire 1000h, negative TTL 5m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver dns200.anycast.me is one of the listed nameservers.
  • ✓ Contact tech@ovh.net #25
    The SOA RNAME tech.ovh.net means tech@ovh.net.
  • ✓ Timestamp serial #26
    The serial 2088166193 is a Unix timestamp (2036-03-03 14:09 UTC).

DNSSEC

warn

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

Records

warn

11 records at the apex

Found

Read from
46.105.206.200:53
TypeValueTTL
SOAdns200.anycast.me. tech.ovh.net. 2088166193 86400 3600 3600000 3003600
NSdns200.anycast.me.3600
NSns200.anycast.me.3600
A213.186.33.53600
MX1 verviers-be.mail.protection.outlook.com.60
TXT"_globalsign-domain-verification=YKTG5-KOk9kl6XeMrpFsdmnZrNBC-gCLaKp5zllLAY"600
TXT"google-site-verification=cA92JgBCv8SyeJUBUmG3xZagDcO46dnZfCn1wYCpN4g"600
TXT"4|https://www.verviers.be"600
TXT"brevo-code:adfa4b1d197d45cb08f572331389874e"600
TXT"MS=6F3FC427F518B5CD1497E771A623A42AEE8DC0DC"600
TXT"v=spf1 a ip4:81.246.113.224 include:imio.be include:spf.protection.outlook.com -all"600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (1m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 1h; 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