enercity.de

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

warn

ns.htp-tel.de, ns2.htp-tel.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns.htp-tel.de, ns2.htp-tel.de
NS in the zone
ns.htp-tel.de, ns1.htp-tel.de, ns2.htp-tel.de
NameserverAddressesNetwork (AS)Glue
ns.htp-tel.de81.14.244.10 2a02:560:2:140::10AS13045 HTP-AS - htp GmbH, DE AS13045 HTP-AS - htp GmbH, DE81.14.244.10 2a02:560:2:140::10
ns1.htp-tel.de (zone only)81.14.243.10 2a02:560:2:100::10AS13045 HTP-AS - htp GmbH, DE AS13045 HTP-AS - htp GmbH, DE-
ns2.htp-tel.de212.59.54.188 2a02:560:2:180::10AS13045 HTP-AS - htp GmbH, DE AS13045 HTP-AS - htp GmbH, DE212.59.54.188 2a02:560:2:180::10

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: ns.htp-tel.de, ns2.htp-tel.de.
    #6
  • !
    NS sets differ
    The nameservers at the parent and in the zone should be the same. Only in the zone: ns1.htp-tel.de. ns.htp-tel.de, ns1.htp-tel.de, ns2.htp-tel.de report NS ns.htp-tel.de ns1.htp-tel.de ns2.htp-tel.de.
    #7
  • ✓ 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 2a02:560:2::/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 (AS13045 (HTP-AS - htp GmbH, DE): 6 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

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns.htp-tel.de 81.14.244.10NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns.htp-tel.de 2a02:560:2:140::10NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns1.htp-tel.de 81.14.243.10NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns1.htp-tel.de 2a02:560:2:100::10NOERROR, 10 ms, authoritativenoyes / yesrefused-
ns2.htp-tel.de 212.59.54.188NOERROR, 9 ms, authoritativenoyes / yesrefused-
ns2.htp-tel.de 2a02:560:2:180::10NOERROR, 10 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 6 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 2026102103 · primary ns.htp-tel.de

Found

Primary (MNAME)
ns.htp-tel.de
Contact (RNAME)
domainmaster.htp.net
Serial
2026102103
Refresh / retry
43200 s / 7200 s
Expire
1209600 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
ns.htp-tel.de (81.14.244.10)2026102103
ns.htp-tel.de (2a02:560:2:140::10)2026102103
ns1.htp-tel.de (81.14.243.10)2026102103
ns1.htp-tel.de (2a02:560:2:100::10)2026102103
ns2.htp-tel.de (212.59.54.188)2026102103
ns2.htp-tel.de (2a02:560:2:180::10)2026102103

Checks

  • ✓ Serial 2026102103 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 2h, expire 14d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns.htp-tel.de is one of the listed nameservers.
  • ✓ Contact domainmaster@htp.net #25
    The SOA RNAME domainmaster.htp.net means domainmaster@htp.net.
  • ✓ Date-based serial #26
    The serial 2026102103 follows the YYYYMMDDnn convention (2026-10-21).

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

16 records at the apex

Found

Read from
81.14.244.10:53
TypeValueTTL
SOAns.htp-tel.de. domainmaster.htp.net. 2026102103 43200 7200 1209600 36003600
NSns.htp-tel.de.3600
NSns2.htp-tel.de.3600
NSns1.htp-tel.de.3600
A212.59.35.1513600
MX100 enercity-de.mail.protection.outlook.com.3600
TXT"v=spf1 ip4:212.59.45.34 include:spf.protection.outlook.com include:mail.zendesk.com ip4:81.95.3.80 ~all"3600
TXT"ms-domain-verification=86a26272-178e-45b5-a2d9-57da06a012c5"3600
TXT"mentimeter-d38cabaf-6f6d-46e8-9d81-cc8f62ff7ea6"3600
TXT"google-site-verification=gzKYkX6KfeiYp7CBTHwfGR-ItnIe1-hHJpR4FDSQA54"3600
TXT"asv=70ab784772f5fe586b60500ebb2bca80"3600
TXT"ms-domain-verification=b7103e9c-1a84-411a-ac58-23a6f2159a67"3600
TXT"_telesec-domain-validation=359809_2026-04-07_gQdnbyAfYoe5rE3YJjA4wkIpExniHHhtEsUigxB9sH1vMFklWz"3600
TXT"google-site-verification=5k10JEfGmnCblDc8u9S7vBusUIH-dV8n5mLxfEuETCE"3600
TXT"miro-verification=139376c441a13380eee94bf4c0c2e0737805ae7f"3600
TXT"figma-domain-verification=34fab2926cc6822d210f14194bee6d080a05bdabc9e408d356c5f2515a670921-1768980200"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.
  • ✓ 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