celle.de

Checked 21 October 2026, 22:06 UTC · via 8.8.8.8
!Passed with warnings
22 passed 2 warnings 0 failed 5 info

Registration

info

.de country-code

Found

TLD
.de (country-code)
ICANN policies apply
no

Checks

  • i
    .de 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
    .de is delegated in the root zone and DNSSEC-signed.
  • i
    Registration data not available
    No registration data via RDAP: the registry of .de offers no RDAP service. Many ccTLD registries don't offer RDAP; check the registry's WHOIS instead.
    #3

Delegation

info

ns1.advantic.net, ns2.advantic.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.advantic.net, ns2.advantic.net
NS in the zone
ns1.advantic.net, ns2.advantic.net
NameserverAddressesNetwork (AS)Glue
ns1.advantic.net213.178.84.120 2a00:12d0:2500:78::1AS13101 TNG-AS - TNG Stadtnetz GmbH, DE AS13101 TNG-AS - TNG Stadtnetz GmbH, DE-
ns2.advantic.net217.7.11.130 2003:59:23::10AS3320 DTAG - Deutsche Telekom AG, DE AS3320 DTAG - Deutsche Telekom AG, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.advantic.net, ns2.advantic.net.
    #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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS13101 (TNG-AS - TNG Stadtnetz GmbH, DE): 2 addresses; AS3320 (DTAG - Deutsche Telekom AG, DE): 2 addresses.
  • i
    All nameserver names under .net
    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

warn

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.advantic.net 213.178.84.120NOERROR, 14 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:44 by root@localhost)
ns1.advantic.net 2a00:12d0:2500:78::1NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:44 by root@localhost)
ns2.advantic.net 217.7.11.130NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:03 by root@localhost)
ns2.advantic.net 2003:59:23::10NOERROR, 14 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:03 by root@localhost)

Checks

  • ✓ All respond #14
    All 4 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: ns1.advantic.net: "PowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:44 by root@localhost)"; ns2.advantic.net: "PowerDNS Authoritative Server 5.0.7 (built Aug 5 2026 13:25:03 by root@localhost)". 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.

SOA

pass

serial 2026042001 · primary ns1.advantic.net

Found

Primary (MNAME)
ns1.advantic.net
Contact (RNAME)
admin.celle.de
Serial
2026042001
Refresh / retry
14400 s / 7200 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.advantic.net (213.178.84.120)2026042001
ns1.advantic.net (2a00:12d0:2500:78::1)2026042001
ns2.advantic.net (217.7.11.130)2026042001
ns2.advantic.net (2003:59:23::10)2026042001

Checks

  • ✓ Serial 2026042001 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 2h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.advantic.net is one of the listed nameservers.
  • ✓ Contact admin@celle.de #25
    The SOA RNAME admin.celle.de means admin@celle.de.
  • ✓ Date-based serial #26
    The serial 2026042001 follows the YYYYMMDDnn convention (2026-04-20).

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

info

11 records at the apex

Found

Read from
213.178.84.120:53
TypeValueTTL
SOAns1.advantic.net. admin.celle.de. 2026042001 14400 7200 604800 864003600
NSns1.advantic.net.3600
NSns2.advantic.net.3600
A213.178.85.1783600
MX10 mta1in.kdo.de.300
MX10 mta2in.kdo.de.300
TXT"apple-domain-verification=vtlQmCOWBlZEXcQ7"3600
TXT"logmein-verification-code=a27a8d7b-719d-4e20-838c-8e2237e67582"3600
TXT"apple-domain-verification=IN6lR9K0IyNKLBnv"3600
TXT"google-site-verification=n3feGxycBF4AHrIVz2T2yOeR4tZIoIB0V-sX14B8hRo"3600
TXT"v=spf1 include:spf.mailjet.com include:_spf.kdo.de include:nol-is.de include:mail.advantic.de ip4:194.76.65.115 include:spf.itebo.de -all"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 5m, NS 1h. The NS TTL at the parent is 1d and in the zone 1h; resolvers may use either.
  • ✓ 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