vodafone.de

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

ns1.vodafone.com, ns3.vodafone.com, ns5.vodafone.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.vodafone.com, ns3.vodafone.com, ns5.vodafone.com
NS in the zone
ns1.vodafone.com, ns3.vodafone.com, ns5.vodafone.com
NameserverAddressesNetwork (AS)Glue
ns1.vodafone.com47.73.65.141AS1273 CW - IDDQD-AS, EU-
ns3.vodafone.com47.73.20.173AS1273 CW - IDDQD-AS, EU-
ns5.vodafone.com47.73.31.237AS201917 VF-GROUP-DC1 - Vodafone Group Services GmbH, DE-

Checks

  • ✓ 3 nameservers #6
    Delegated to ns1.vodafone.com, ns3.vodafone.com, ns5.vodafone.com.
  • ✓ 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 0 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS1273 (CW - IDDQD-AS, EU): 2 addresses; AS201917 (VF-GROUP-DC1 - Vodafone Group Services GmbH, DE): 1 address.
  • i
    All nameserver names under .com
    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

3 of 3 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.vodafone.com 47.73.65.141NOERROR, 14 ms, authoritativenoyes / yesrefused-
ns3.vodafone.com 47.73.20.173NOERROR, 24 ms, authoritativenoyes / yesrefused-
ns5.vodafone.com 47.73.31.237NOERROR, 20 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 3 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

info

serial 2008078059 · primary ns-admin.vodafone.com

Found

Primary (MNAME)
ns-admin.vodafone.com
Contact (RNAME)
hostmaster.vodafone.com
Serial
2008078059
Refresh / retry
14400 s / 1440 s
Expire
604800 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.vodafone.com (47.73.65.141)2008078059
ns3.vodafone.com (47.73.20.173)2008078059
ns5.vodafone.com (47.73.31.237)2008078059

Checks

  • ✓ Serial 2008078059 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 24m, expire 7d, negative TTL 15m.
  • i
    Hidden master
    The primary nameserver ns-admin.vodafone.com is not listed as a nameserver: a hidden master that only feeds the public secondaries. That is a common setup; make sure it is not reachable for zone transfers from outside.
    #24
  • ✓ Contact hostmaster@vodafone.com #25
    The SOA RNAME hostmaster.vodafone.com means hostmaster@vodafone.com.
  • ✓ Timestamp serial #26
    The serial 2008078059 is a Unix timestamp (2033-08-19 15:27 UTC).

DNSSEC

warn

Signed, DS published at parent

Found

Validated by resolver
yes
Denial of existence
NSEC3
NSEC3
10 iterations, 13-byte salt
Signatures valid until
7 August 2027

DS at the parent

Key tagAlgorithmDigestMatches a key
4732RSASHA256 (8)SHA256 9338AC4266FCD231…yes

DNSKEY in the zone

Key tagRoleAlgorithm
27891ZSK (256)RSASHA256 (8)
31459ZSK (256)RSASHA256 (8)
4732KSK (257)RSASHA256 (8)

Checks

  • ✓ Signed and validated #27
    The zone is signed, the parent publishes a DS record, and the resolver validates the answers.
  • ✓ DS matches a key #28
    The DS record at the parent matches a key in the zone: key tag 4732 (SHA256).
  • ✓ Modern algorithms #29
    Key algorithms: RSASHA256 (8).
  • ✓ Signatures valid until 2027-08-07 #30
    The earliest DNSKEY/SOA signature expires at 2027-08-07 20:28 UTC.
  • !
    NSEC3 with extra iterations or salt
    NSEC3 uses 10 iterations and a 13-byte salt. RFC 9276 recommends 0 iterations and no salt: extra iterations cost resolvers CPU and add no real protection, and some validators treat high counts as insecure.
    #31

Records

info

12 records at the apex

Found

Read from
47.73.65.141:53
TypeValueTTL
SOAns-admin.vodafone.com. hostmaster.vodafone.com. 2008078059 14400 1440 604800 90086400
NSns5.vodafone.com.86400
NSns3.vodafone.com.86400
NSns1.vodafone.com.86400
A45.60.74.1141800
MX10 mx1.vodafonemail.de.86400
MX10 mx2.vodafonemail.de.86400
MX10 mx3.vodafonemail.de.86400
TXT"google-site-verification=qsGzQj0ODvtTpTqpSGT8_5EyD39gnnVvhtRmr2_S8fE"300
TXT"docusign=44e2773f-ee4e-49b3-b749-db7d1603d291"300
TXT"docusign=88289509-099c-4519-a968-9f6f9d47b1b7"300
TXT"v=spf1 include:vodafonemail.de ip4:176.95.8.68 ip4:84.17.184.251 ip4:84.17.184.252 ip4:84.17.184.253 include:spf1.vodafone.de -all"300

Checks

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