itb-berlin.de

Checked 21 October 2026, 23:00 UTC · via 8.8.8.8
!Passed with warnings
22 passed 3 warnings 0 failed 4 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

managed-ip01.ns15.net, managed-ip02.ns15.net, managed-ip03.ns15.net, managed-ip04.ns15.net

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
managed-ip01.ns15.net, managed-ip02.ns15.net, managed-ip03.ns15.net, managed-ip04.ns15.net
NS in the zone
managed-ip01.ns15.net, managed-ip02.ns15.net, managed-ip03.ns15.net, managed-ip04.ns15.net
NameserverAddressesNetwork (AS)Glue
managed-ip01.ns15.net62.116.159.66 2001:4178:3:a357:62:116:159:66AS15456 INTERNETX-AS - InterNetX GmbH, DE AS15456 INTERNETX-AS - InterNetX GmbH, DE-
managed-ip02.ns15.net217.160.113.99 2001:8d8:580:401:217:160:113:99AS8560 IONOS-AS - IONOS SE, DE AS8560 IONOS-AS - IONOS SE, DE-
managed-ip03.ns15.net89.146.248.64 2a01:130:2000:118:89:146:248:64AS8495 INTERNET_AG - INTERNET AG Global Network, DE AS8495 INTERNET_AG - INTERNET AG Global Network, DE-
managed-ip04.ns15.net89.146.248.64 2a01:130:2000:118:89:146:248:64AS8495 INTERNET_AG - INTERNET AG Global Network, DE AS8495 INTERNET_AG - INTERNET AG Global Network, DE-

Checks

  • ✓ 4 nameservers #6
    Delegated to managed-ip01.ns15.net, managed-ip02.ns15.net, managed-ip03.ns15.net, managed-ip04.ns15.net.
  • ✓ 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 3 IPv4 /24s and 3 IPv6 /48s.
  • ✓ 3 autonomous systems #11
    The nameservers are spread over: AS15456 (INTERNETX-AS - InterNetX GmbH, DE): 2 addresses; AS8495 (INTERNET_AG - INTERNET AG Global Network, DE): 4 addresses; AS8560 (IONOS-AS - IONOS SE, 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

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
managed-ip01.ns15.net 62.116.159.66NOERROR, 10 ms, authoritativenoyes / yesrefused-
managed-ip01.ns15.net 2001:4178:3:a357:62:116:159:66NOERROR, 16 ms, authoritativenoyes / yesrefused-
managed-ip02.ns15.net 217.160.113.99NOERROR, 8 ms, authoritativenoyes / yesrefused-
managed-ip02.ns15.net 2001:8d8:580:401:217:160:113:99NOERROR, 8 ms, authoritativenoyes / yesrefused-
managed-ip03.ns15.net 89.146.248.64NOERROR, 4 ms, authoritativenoyes / yesrefused-
managed-ip03.ns15.net 2a01:130:2000:118:89:146:248:64NOERROR, 8 ms, authoritativenoyes / yesrefused-
managed-ip04.ns15.net 89.146.248.64NOERROR, 3 ms, authoritativenoyes / yesrefused-
managed-ip04.ns15.net 2a01:130:2000:118:89:146:248:64NOERROR, 8 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 2026090300 · primary managed-ip01.ns15.net

Found

Primary (MNAME)
managed-ip01.ns15.net
Contact (RNAME)
domainadmin.managed-ip.com
Serial
2026090300
Refresh / retry
3600 s / 3600 s
Expire
2419200 s
Negative TTL
300 s

Serial per nameserver

NameserverSerial
managed-ip01.ns15.net (62.116.159.66)2026090300
managed-ip01.ns15.net (2001:4178:3:a357:62:116:159:66)2026090300
managed-ip02.ns15.net (217.160.113.99)2026090300
managed-ip02.ns15.net (2001:8d8:580:401:217:160:113:99)2026090300
managed-ip03.ns15.net (89.146.248.64)2026090300
managed-ip03.ns15.net (2a01:130:2000:118:89:146:248:64)2026090300
managed-ip04.ns15.net (89.146.248.64)2026090300
managed-ip04.ns15.net (2a01:130:2000:118:89:146:248:64)2026090300

Checks

  • ✓ Serial 2026090300 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    retry 1h should be shorter than refresh 1h. Current values: refresh 1h, retry 1h, expire 28d, negative TTL 5m.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver managed-ip01.ns15.net is one of the listed nameservers.
  • ✓ Contact domainadmin@managed-ip.com #25
    The SOA RNAME domainadmin.managed-ip.com means domainadmin@managed-ip.com.
  • ✓ Date-based serial #26
    The serial 2026090300 follows the YYYYMMDDnn convention (2026-09-03).

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

10 records at the apex

Found

Read from
62.116.159.66:53
TypeValueTTL
SOAmanaged-ip01.ns15.net. domainadmin.managed-ip.com. 2026090300 3600 3600 2419200 300300
NSmanaged-ip01.ns15.net.300
NSmanaged-ip04.ns15.net.300
NSmanaged-ip03.ns15.net.300
NSmanaged-ip02.ns15.net.300
A85.236.56.24660
AAAA2001:4178:2:1294:85:236:56:24660
MX0 itbberlin-de0i.mail.protection.outlook.com.300
TXT"v=spf1 include:spf.protection.outlook.com -all"300
TXT"MS=ms46856090"300

Checks

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