transmediale.de

Checked 22 October 2026, 00:41 UTC · via 8.8.8.8
!Passed with warnings
21 passed 1 warning 0 failed 7 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.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de, ns4.in-berlin.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de, ns4.in-berlin.de
NS in the zone
ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de, ns4.in-berlin.de
NameserverAddressesNetwork (AS)Glue
ns1.in-berlin.de192.109.42.26 2001:67c:1400:1010::42:26AS29670 IN-BERLIN-AS - Individual Network Berlin (_IN-Berlin_) e.V., DE AS29670 IN-BERLIN-AS - Individual Network Berlin (_IN-Berlin_) e.V., DE192.109.42.26 2001:67c:1400:1010::42:26
ns2.in-berlin.de217.197.80.34 2001:67c:1400:1010::34AS29670 IN-BERLIN-AS - Individual Network Berlin (_IN-Berlin_) e.V., DE AS29670 IN-BERLIN-AS - Individual Network Berlin (_IN-Berlin_) e.V., DE217.197.80.34 2001:67c:1400:1010::34
ns3.in-berlin.de193.29.188.4 2001:67c:1403:1010::4AS29670 IN-BERLIN-AS - Individual Network Berlin (_IN-Berlin_) e.V., DE AS29670 IN-BERLIN-AS - Individual Network Berlin (_IN-Berlin_) e.V., DE193.29.188.4 2001:67c:1403:1010::4
ns4.in-berlin.de130.133.8.36AS680 DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE130.133.8.36

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.in-berlin.de, ns2.in-berlin.de, ns3.in-berlin.de, ns4.in-berlin.de.
  • ✓ 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 4 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS29670 (IN-BERLIN-AS - Individual Network Berlin (_IN-Berlin_) e.V., DE): 6 addresses; AS680 (DFN - Verein zur Foerderung eines Deutschen Forschungsnetzes e.V., DE): 1 address.
  • 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
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns4.in-berlin.de.
    #13

Nameservers

info

7 of 7 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.in-berlin.de 192.109.42.26NOERROR, 13 ms, authoritativenoyes / yesrefusedIN-Berlin DNS
ns1.in-berlin.de 2001:67c:1400:1010::42:26NOERROR, 13 ms, authoritativenoyes / yesrefusedIN-Berlin DNS
ns2.in-berlin.de 217.197.80.34NOERROR, 11 ms, authoritativenoyes / yesrefusedIN-Berlin DNS
ns2.in-berlin.de 2001:67c:1400:1010::34NOERROR, 12 ms, authoritativenoyes / yesrefusedIN-Berlin DNS
ns3.in-berlin.de 193.29.188.4NOERROR, 19 ms, authoritativenoyes / yesrefusedIN-Berlin DNS
ns3.in-berlin.de 2001:67c:1403:1010::4NOERROR, 13 ms, authoritativenoyes / yesrefusedIN-Berlin DNS
ns4.in-berlin.de 130.133.8.36NOERROR, 20 ms, authoritativenoyes / yesrefusedIN-Berlin DNS

Checks

  • ✓ All respond #14
    All 7 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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.in-berlin.de: "IN-Berlin DNS"; ns2.in-berlin.de: "IN-Berlin DNS"; ns3.in-berlin.de: "IN-Berlin DNS"; ns4.in-berlin.de: "IN-Berlin DNS".
    #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 2026092918 · primary ns1.in-berlin.de

Found

Primary (MNAME)
ns1.in-berlin.de
Contact (RNAME)
domain.in-berlin.de
Serial
2026092918
Refresh / retry
28800 s / 1800 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns1.in-berlin.de (192.109.42.26)2026092918
ns1.in-berlin.de (2001:67c:1400:1010::42:26)2026092918
ns2.in-berlin.de (217.197.80.34)2026092918
ns2.in-berlin.de (2001:67c:1400:1010::34)2026092918
ns3.in-berlin.de (193.29.188.4)2026092918
ns3.in-berlin.de (2001:67c:1403:1010::4)2026092918
ns4.in-berlin.de (130.133.8.36)2026092918

Checks

  • ✓ Serial 2026092918 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 8h, retry 30m, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.in-berlin.de is one of the listed nameservers.
  • ✓ Contact domain@in-berlin.de #25
    The SOA RNAME domain.in-berlin.de means domain@in-berlin.de.
  • ✓ Date-based serial #26
    The serial 2026092918 follows the YYYYMMDDnn convention (2026-09-29).

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

12 records at the apex

Found

Read from
192.109.42.26:53
TypeValueTTL
SOAns1.in-berlin.de. domain.in-berlin.de. 2026092918 28800 1800 1209600 36003600
NSns1.in-berlin.de.3600
NSns4.in-berlin.de.3600
NSns3.in-berlin.de.3600
NSns2.in-berlin.de.3600
A159.69.186.1583600
MX30 mx3.in-berlin.de.3600
MX40 mx4.in-berlin.de.3600
MX10 mx1.in-berlin.de.3600
MX20 mx2.in-berlin.de.3600
TXT"v=spf1 include:_spf.in-berlin.de ip4:46.101.143.68 -all"3600
TXT"google-site-verification=QmKon2Tmqs2i3Sg74c1Iq2uxU4NtRWFLWQGdKmDxUcs"3600

Checks

  • ✓ TTLs within range #32
    TTLs: A 1h, MX 1h, 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.
  • 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