intel.de

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

warn

ns1.intel.com, ns2.intel.com, ns3.intel.com, ns4.intel.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
ns1.intel.com, ns2.intel.com, ns3.intel.com, ns4.intel.com
NS in the zone
ns1.intel.com, ns2.intel.com, ns3.intel.com, ns4.intel.com
NameserverAddressesNetwork (AS)Glue
ns1.intel.com192.55.52.33AS4983 INTEL-SC-AS - Intel Corporation, US-
ns2.intel.com134.191.190.35AS4983 INTEL-SC-AS - Intel Corporation, US-
ns3.intel.com192.198.148.13AS4983 INTEL-SC-AS - Intel Corporation, US-
ns4.intel.com192.102.198.240AS4983 INTEL-SC-AS - Intel Corporation, US-

Checks

  • ✓ 4 nameservers #6
    Delegated to ns1.intel.com, ns2.intel.com, ns3.intel.com, ns4.intel.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 0 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS4983 (INTEL-SC-AS - Intel Corporation, US): 4 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 .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

4 of 4 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
ns1.intel.com 192.55.52.33NOERROR, 162 ms, authoritativenoyes / yesrefused-
ns2.intel.com 134.191.190.35NOERROR, 28 ms, authoritativenoyes / yesrefused-
ns3.intel.com 192.198.148.13NOERROR, 215 ms, authoritativenoyes / yesrefused-
ns4.intel.com 192.102.198.240NOERROR, 167 ms, authoritativenoyes / yesrefused-

Checks

  • ✓ All respond #14
    All 4 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 2026092101 · primary ns1.intel.com

Found

Primary (MNAME)
ns1.intel.com
Contact (RNAME)
hostmaster.intel.com
Serial
2026092101
Refresh / retry
43200 s / 300 s
Expire
1209600 s
Negative TTL
900 s

Serial per nameserver

NameserverSerial
ns1.intel.com (192.55.52.33)2026092101
ns2.intel.com (134.191.190.35)2026092101
ns3.intel.com (192.198.148.13)2026092101
ns4.intel.com (192.102.198.240)2026092101

Checks

  • ✓ Serial 2026092101 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 12h, retry 5m, expire 14d, negative TTL 15m.
  • ✓ Primary is a public nameserver #24
    The primary nameserver ns1.intel.com is one of the listed nameservers.
  • ✓ Contact hostmaster@intel.com #25
    The SOA RNAME hostmaster.intel.com means hostmaster@intel.com.
  • ✓ Date-based serial #26
    The serial 2026092101 follows the YYYYMMDDnn convention (2026-09-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

10 records at the apex

Found

Read from
192.55.52.33:53
TypeValueTTL
SOAns1.intel.com. hostmaster.intel.com. 2026092101 43200 300 1209600 90010800
NSns3.intel.com.900
NSns4.intel.com.900
NSns1.intel.com.900
NSns2.intel.com.900
A13.91.95.74900
MX100 mtab.intel.com.900
TXT"google-site-verification=J0-JyOtaVARvv7tIvEM_oGY5lm7UAjSYy2y8imNwHR8"900
TXT"v=spf1 include:_spf.intel.com -all"900
TXT"facebook-domain-verification=gn5cbyibpfulorgcg3acxj4z4v8y3y"900

Checks

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