webgo.de

Checked 22 October 2026, 01:00 UTC · via 8.8.8.8
!Passed with warnings
21 passed 3 warnings 0 failed 5 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.webgo.de, ns2.webgo.de, ns3.webgo.de, ns4.webgo.de

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.webgo.de, ns2.webgo.de, ns3.webgo.de, ns4.webgo.de
NS in the zone
ns1.webgo.de, ns2.webgo.de, ns3.webgo.de, ns4.webgo.de
NameserverAddressesNetwork (AS)Glue
ns1.webgo.de89.44.8.112 2a00:5fc1:0:120:89:44:8:112AS48324 DE-WEBGO - webgo GmbH, DE AS48324 DE-WEBGO - webgo GmbH, DE89.44.8.112 2a00:5fc1:0:120:89:44:8:112
ns2.webgo.de89.44.8.111 2a00:5fc1:0:120:89:44:8:111AS48324 DE-WEBGO - webgo GmbH, DE AS48324 DE-WEBGO - webgo GmbH, DE89.44.8.111 2a00:5fc1:0:120:89:44:8:111
ns3.webgo.de89.44.8.124 2a00:5fc1:0:120:89:44:8:124AS48324 DE-WEBGO - webgo GmbH, DE AS48324 DE-WEBGO - webgo GmbH, DE89.44.8.124 2a00:5fc1:0:120:89:44:8:124
ns4.webgo.de217.79.184.5 2001:4ba0:ffff:81::1AS24961 MYLOC-AS - WIIT AG, DE AS24961 MYLOC-AS - WIIT AG, DE217.79.184.5 2001:4ba0:ffff:81::1

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.webgo.de, ns2.webgo.de, ns3.webgo.de, ns4.webgo.de.
  • ✓ Parent and zone agree #7
    The parent delegation and the zone's NS records list the same nameservers.
  • ✓ Glue present and correct #8
    Glue is published for the nameservers inside the zone: ns1.webgo.de, ns2.webgo.de, ns3.webgo.de, ns4.webgo.de.
  • ✓ 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 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS24961 (MYLOC-AS - WIIT AG, DE): 2 addresses; AS48324 (DE-WEBGO - webgo GmbH, DE): 6 addresses.
  • 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

warn

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.webgo.de 89.44.8.112NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns1.webgo.de 2a00:5fc1:0:120:89:44:8:112NOERROR, 11 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns2.webgo.de 89.44.8.111NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns2.webgo.de 2a00:5fc1:0:120:89:44:8:111NOERROR, 12 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns3.webgo.de 89.44.8.124NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns3.webgo.de 2a00:5fc1:0:120:89:44:8:124NOERROR, 13 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns4.webgo.de 217.79.184.5NOERROR, 8 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3
ns4.webgo.de 2001:4ba0:ffff:81::1NOERROR, 9 ms, authoritativenoyes / yesrefusedPowerDNS Authoritative Server 4.7.3

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.
  • !
    Software version disclosed
    These nameservers report their software version via version.bind/version.server, which helps attackers find known vulnerabilities: ns1.webgo.de: "PowerDNS Authoritative Server 4.7.3"; ns2.webgo.de: "PowerDNS Authoritative Server 4.7.3"; ns3.webgo.de: "PowerDNS Authoritative Server 4.7.3"; ns4.webgo.de: "PowerDNS Authoritative Server 4.7.3". Hide or replace the version string.
    #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 2026072101 · primary ns1.webgo.de

Found

Primary (MNAME)
ns1.webgo.de
Contact (RNAME)
whois.webgo.de
Serial
2026072101
Refresh / retry
39940 s / 14400 s
Expire
604800 s
Negative TTL
43200 s

Serial per nameserver

NameserverSerial
ns1.webgo.de (89.44.8.112)2026072101
ns1.webgo.de (2a00:5fc1:0:120:89:44:8:112)2026072101
ns2.webgo.de (89.44.8.111)2026072101
ns2.webgo.de (2a00:5fc1:0:120:89:44:8:111)2026072101
ns3.webgo.de (89.44.8.124)2026072101
ns3.webgo.de (2a00:5fc1:0:120:89:44:8:124)2026072101
ns4.webgo.de (217.79.184.5)2026072101
ns4.webgo.de (2001:4ba0:ffff:81::1)2026072101

Checks

  • ✓ Serial 2026072101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 11h5m40s, retry 4h, expire 7d, negative TTL 12h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.webgo.de is one of the listed nameservers.
  • ✓ Contact whois@webgo.de #25
    The SOA RNAME whois.webgo.de means whois@webgo.de.
  • ✓ Date-based serial #26
    The serial 2026072101 follows the YYYYMMDDnn convention (2026-07-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

warn

14 records at the apex

Found

Read from
89.44.8.112:53
TypeValueTTL
SOAns1.webgo.de. whois.webgo.de. 2026072101 39940 14400 604800 4320043200
NSns1.webgo.de.43200
NSns2.webgo.de.43200
NSns4.webgo.de.43200
NSns3.webgo.de.43200
A89.44.8.1387200
MX10 webgo-de.mail.protection.outlook.com.180
TXT"v=spf1 a mx ip4:37.17.224.0/21 ip4:185.30.32.0/22 ip4:88.82.224.0/19 ip4:45.153.56.0/22 include:spf.brevo.com include:143478353.spf05.hubspotemail.net include:spf.protection.outlook.com ~all"3600
TXT"brevo-code:cb58851494b8468f0cf4fda2cfa66ad8"3600
TXT"uber-domain-verification=824696a5-1167-4a0a-9fcb-60b6178a4fd8"3600
TXT"MS=ms14534982"3600
TXT"openai-domain-verification=dv-M0xoMZb0OGLMH9rCGfECKknN"360
TXT"google-site-verification=O1yMWeMJCCMSgbPFJcpveXN3PxnLBUHx29L8AR-bvQw"3600
TXT"google-site-verification=xFn0IZZytipm4SSbgWDz0jnL1SX83pdXvKOHMaKmgbI"3600

Checks

  • !
    Very low TTLs
    These records have a TTL below 5m, causing extra queries and slower lookups: MX (3m). Low TTLs are useful just before a planned change. The NS TTL at the parent is 1d and in the zone 12h; resolvers may use either.
    #32
  • ✓ 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