veolia.de

Checked 22 October 2026, 00:51 UTC · via 8.8.8.8
✗Problems found
21 passed 2 warnings 1 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.iptwins.net, ns2.iptwins.net, ns3.iptwins.com, ns4.iptwins.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.iptwins.net, ns2.iptwins.net, ns3.iptwins.com, ns4.iptwins.com
NS in the zone
ns1.iptwins.net, ns2.iptwins.net, ns3.iptwins.com, ns4.iptwins.com
NameserverAddressesNetwork (AS)Glue
ns1.iptwins.net188.165.162.43AS16276 OVH - OVH SAS, FR-
ns2.iptwins.net193.70.18.204AS16276 OVH - OVH SAS, FR-
ns3.iptwins.com144.217.70.141 2607:5300:203:28d::AS16276 OVH - OVH SAS, FR AS16276 OVH - OVH SAS, FR-
ns4.iptwins.com161.202.174.147 2401:c900:1101:496::3AS36351 SOFTLAYER - IBM Cloud, US AS36351 SOFTLAYER - IBM Cloud, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.iptwins.net, ns2.iptwins.net, ns3.iptwins.com, ns4.iptwins.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 4 IPv4 /24s and 2 IPv6 /48s.
  • ✓ 2 autonomous systems #11
    The nameservers are spread over: AS16276 (OVH - OVH SAS, FR): 4 addresses; AS36351 (SOFTLAYER - IBM Cloud, US): 2 addresses.
  • ✓ Nameserver names under 2 TLDs #12
    Nameserver names use the TLDs .com, .net.
  • i
    Partly IPv6
    These nameservers have no IPv6 address: ns1.iptwins.net, ns2.iptwins.net.
    #13

Nameservers

fail

6 of 6 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.iptwins.net 188.165.162.43NOERROR, 15 ms, authoritativenoyes / yesrefusedSECRET
ns2.iptwins.net 193.70.18.204NOERROR, 16 ms, authoritativenono / yesrefusedSECRET
ns3.iptwins.com 144.217.70.141NOERROR, 97 ms, authoritativenono / yesrefusedSECRET
ns3.iptwins.com 2607:5300:203:28d::NOERROR, 97 ms, authoritativenoyes / yesrefusedSECRET
ns4.iptwins.com 161.202.174.147NOERROR, 176 ms, authoritativenoyes / yesrefusedSECRET
ns4.iptwins.com 2401:c900:1101:496::3NOERROR, 176 ms, authoritativenoyes / yesrefusedSECRET

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.
  • i
    Identifying string disclosed
    These nameservers answer version queries with a string that is not a version number: ns1.iptwins.net: "SECRET"; ns2.iptwins.net: "SECRET"; ns3.iptwins.com: "SECRET"; ns4.iptwins.com: "SECRET".
    #17
  • ✓ Zone transfers refused #18
    No nameserver allows a zone transfer to the public.
  • ✗
    No DNS over TCP
    DNS over TCP is required (RFC 7766); without it, large answers such as DNSSEC responses fail. Not answering over TCP: ns2.iptwins.net (193.70.18.204): read tcp 46.225.38.91:50280->193.70.18.204:53: i/o timeout; ns3.iptwins.com (144.217.70.141): read tcp 46.225.38.91:43584->144.217.70.141:53: i/o timeout.
    #19
  • ✓ EDNS supported #20
    All nameservers support EDNS(0).
  • ✓ Public addresses #21
    All nameserver addresses are publicly routable.

SOA

warn

serial 2026102102 · primary ns1.iptwins.net

Found

Primary (MNAME)
ns1.iptwins.net
Contact (RNAME)
dns-log.iptwins.com
Serial
2026102102
Refresh / retry
86400 s / 7200 s
Expire
2592000 s
Negative TTL
345600 s

Serial per nameserver

NameserverSerial
ns1.iptwins.net (188.165.162.43)2026102102
ns2.iptwins.net (193.70.18.204)2026102102
ns3.iptwins.com (144.217.70.141)2026102102
ns3.iptwins.com (2607:5300:203:28d::)2026102102
ns4.iptwins.com (161.202.174.147)2026102102
ns4.iptwins.com (2401:c900:1101:496::3)2026102102

Checks

  • ✓ Serial 2026102102 everywhere #22
    All nameservers serve the same version of the zone.
  • !
    Unusual SOA timers
    negative caching TTL (minimum) 4d is outside 5m–1d (RFC 2308 recommends 1–3 hours). Current values: refresh 1d, retry 2h, expire 30d, negative TTL 4d.
    #23
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.iptwins.net is one of the listed nameservers.
  • ✓ Contact dns-log@iptwins.com #25
    The SOA RNAME dns-log.iptwins.com means dns-log@iptwins.com.
  • ✓ Date-based serial #26
    The serial 2026102102 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

19 records at the apex

Found

Read from
188.165.162.43:53
TypeValueTTL
SOAns1.iptwins.net. dns-log.iptwins.com. 2026102102 86400 7200 2592000 3456003600
NSns1.iptwins.net.3600
NSns2.iptwins.net.3600
NSns3.iptwins.com.3600
NSns4.iptwins.com.3600
A104.17.242.286400
MX5 alt2.aspmx.l.google.com.3600
MX5 alt1.aspmx.l.google.com.3600
MX1 aspmx.l.google.com.3600
MX10 aspmx2.googlemail.com.3600
MX10 aspmx3.googlemail.com.3600
TXT"v=spf1 include:_spf.google.com -all"1800
TXT"facebook-domain-verification=h7goxcp94lrezlmngojesj140jmtsg"1800
TXT"google-site-verification=XHoiD2z8xXaVilO-owJQTLY6UVew8oz2uM-gOwrNpZE"1800
TXT"google-site-verification=Oyq4eAa1sz9d44BjS_eYNm0c0MzN8BwVULwczMUlHf8"1800
TXT"apple-domain-verification=DaUsTM7Pejuq2Yxp"1800
TXT"3de52d339112432f8505cbefcf5ab632"1800
TXT"cywetadns-domain-verificationcontent=86035cebdc8e22781bee666e45a5730d"1800
TXT"google-site-verification=l6DAI8eqo_Wzj78bhNvbreAo2qGhDQKCmzrB4d5IsBA"1800

Checks

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