mynetcologne.de

Checked 21 October 2026, 23:31 UTC · via 8.8.8.8
!Passed with warnings
20 passed 1 warning 0 failed 8 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.netcologne.de, ns3.netcologne.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.netcologne.de, ns3.netcologne.de
NS in the zone
ns1.netcologne.de, ns3.netcologne.de
NameserverAddressesNetwork (AS)Glue
ns1.netcologne.de194.8.194.70 2001:4dd0:100:1020:53:1:0:1AS8422 NETCOLOGNE - NetCologne Gesellschaft fur Telekommunikation mbH, DE AS8422 NETCOLOGNE - NetCologne Gesellschaft fur Telekommunikation mbH, DE194.8.194.70 2001:4dd0:100:1020:53:1:0:1
ns3.netcologne.de194.8.197.10 2001:4dd0:100:4220:53:1:0:3AS8422 NETCOLOGNE - NetCologne Gesellschaft fur Telekommunikation mbH, DE AS8422 NETCOLOGNE - NetCologne Gesellschaft fur Telekommunikation mbH, DE194.8.197.10 2001:4dd0:100:4220:53:1:0:3

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns1.netcologne.de, ns3.netcologne.de.
    #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.
  • i
    One address family in one network
    all IPv6 addresses are in 2001:4dd0:100::/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 (AS8422 (NETCOLOGNE - NetCologne Gesellschaft fur Telekommunikation mbH, DE): 4 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 .de
    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

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.netcologne.de 194.8.194.70NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns1.netcologne.de 2001:4dd0:100:1020:53:1:0:1NOERROR, 8 ms, authoritativenoyes / yesrefused-
ns3.netcologne.de 194.8.197.10NOERROR, 7 ms, authoritativenoyes / yesrefused-
ns3.netcologne.de 2001:4dd0:100:4220:53:1:0:3NOERROR, 7 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 2022041101 · primary ns1.netcologne.de

Found

Primary (MNAME)
ns1.netcologne.de
Contact (RNAME)
hostmaster.netcologne.de
Serial
2022041101
Refresh / retry
10800 s / 3600 s
Expire
604800 s
Negative TTL
86400 s

Serial per nameserver

NameserverSerial
ns1.netcologne.de (194.8.194.70)2022041101
ns1.netcologne.de (2001:4dd0:100:1020:53:1:0:1)2022041101
ns3.netcologne.de (194.8.197.10)2022041101
ns3.netcologne.de (2001:4dd0:100:4220:53:1:0:3)2022041101

Checks

  • ✓ Serial 2022041101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 3h, retry 1h, expire 7d, negative TTL 1d.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.netcologne.de is one of the listed nameservers.
  • ✓ Contact hostmaster@netcologne.de #25
    The SOA RNAME hostmaster.netcologne.de means hostmaster@netcologne.de.
  • ✓ Date-based serial #26
    The serial 2022041101 follows the YYYYMMDDnn convention (2022-04-11).

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

5 records at the apex

Found

Read from
194.8.194.70:53
TypeValueTTL
SOAns1.netcologne.de. hostmaster.netcologne.de. 2022041101 10800 3600 604800 8640086400
NSns3.netcologne.de.86400
NSns1.netcologne.de.86400
A81.173.246.8600
AAAA2001:4dd0:100:1023:80:3:0:3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 10m, AAAA 10m, NS 1d.
  • ✓ 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