pharmazeutische-zeitung.de

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

mainware-ns1.ns.tgc.de, mainware-ns2.ns.tgc.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
mainware-ns1.ns.tgc.de, mainware-ns2.ns.tgc.de
NS in the zone
mainware-ns1.ns.tgc.de, mainware-ns2.ns.tgc.de
NameserverAddressesNetwork (AS)Glue
mainware-ns1.ns.tgc.de194.45.26.25AS15844 TGC-AS - true global communications GmbH, DE-
mainware-ns2.ns.tgc.de217.24.0.100AS15844 TGC-AS - true global communications GmbH, DE-

Checks

  • i
    2 nameservers
    Two nameservers meet the minimum; RFC 2182 recommends three or more for important zones: mainware-ns1.ns.tgc.de, mainware-ns2.ns.tgc.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.
  • ✓ Nameservers in different networks #10
    The nameservers are spread over 2 IPv4 /24s and 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS15844 (TGC-AS - true global communications GmbH, DE): 2 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
  • !
    No IPv6
    None of the nameservers has an IPv6 address, so IPv6-only resolvers can't reach them.
    #13

Nameservers

pass

2 of 2 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
mainware-ns1.ns.tgc.de 194.45.26.25NOERROR, 5 ms, authoritativenoyes / yesrefused-
mainware-ns2.ns.tgc.de 217.24.0.100NOERROR, 4 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 2 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 2003040677 · primary mainware-ns1.ns.tgc.de

Found

Primary (MNAME)
mainware-ns1.ns.tgc.de
Contact (RNAME)
admin.tgnet.de
Serial
2003040677
Refresh / retry
86400 s / 14400 s
Expire
2419200 s
Negative TTL
172800 s

Serial per nameserver

NameserverSerial
mainware-ns1.ns.tgc.de (194.45.26.25)2003040677
mainware-ns2.ns.tgc.de (217.24.0.100)2003040677

Checks

  • ✓ Serial 2003040677 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 2d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 4h, expire 28d, negative TTL 2d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver mainware-ns1.ns.tgc.de is one of the listed nameservers.
  • ✓ Contact admin@tgnet.de #25
    The SOA RNAME admin.tgnet.de means admin@tgnet.de.
  • ✓ Date-based serial #26
    The serial 2003040677 follows the YYYYMMDDnn convention (2003-04-06).

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

7 records at the apex

Found

Read from
194.45.26.25:53
TypeValueTTL
SOAmainware-ns1.ns.tgc.de. admin.tgnet.de. 2003040677 86400 14400 2419200 172800172800
NSmainware-ns2.ns.tgc.de.172800
NSmainware-ns1.ns.tgc.de.172800
A37.61.206.33172800
MX10 mail1.1mx.de.172800
TXT"google-site-verification=UK0YySjlNR4GsHbLkFxiRJ3FPhNQG1XD1aoDbqapJJk"3600
TXT"ufi55f1n3432ukau5dsi29hlf7"172800

Checks

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