instagram.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

info

a.ns.facebook.com, b.ns.facebook.com, c.ns.facebook.com, d.ns.facebook.com

Found

Parent zone
de
Delegation from
a.nic.de (194.0.0.53)
NS at the parent
a.ns.facebook.com, b.ns.facebook.com, c.ns.facebook.com, d.ns.facebook.com
NS in the zone
a.ns.facebook.com, b.ns.facebook.com, c.ns.facebook.com, d.ns.facebook.com
NameserverAddressesNetwork (AS)Glue
a.ns.facebook.com129.134.30.12 2a03:2880:f0fc:c:face:b00c:0:35AS32934 FACEBOOK - Facebook, Inc., US AS32934 FACEBOOK - Facebook, Inc., US-
b.ns.facebook.com129.134.31.12 2a03:2880:f0fd:c:face:b00c:0:35AS32934 FACEBOOK - Facebook, Inc., US AS32934 FACEBOOK - Facebook, Inc., US-
c.ns.facebook.com185.89.218.12 2a03:2880:f1fc:c:face:b00c:0:35AS32934 FACEBOOK - Facebook, Inc., US AS32934 FACEBOOK - Facebook, Inc., US-
d.ns.facebook.com185.89.219.12 2a03:2880:f1fd:c:face:b00c:0:35AS32934 FACEBOOK - Facebook, Inc., US AS32934 FACEBOOK - Facebook, Inc., US-

Checks

  • ✓ 4 nameservers #6
    Delegated to a.ns.facebook.com, b.ns.facebook.com, c.ns.facebook.com, d.ns.facebook.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 4 IPv6 /48s.
  • i
    All nameservers in one AS
    All nameserver addresses are announced by one network operator (AS32934 (FACEBOOK - Facebook, Inc., US): 8 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
  • ✓ All reachable over IPv6 #13
    Every nameserver has an IPv6 address.

Nameservers

pass

8 of 8 addresses answer authoritatively

Found

NameserverAnswerRecursionTCP / EDNSAXFRVersion
a.ns.facebook.com 129.134.30.12NOERROR, 6 ms, authoritativenoyes / yesrefused-
a.ns.facebook.com 2a03:2880:f0fc:c:face:b00c:0:35NOERROR, 6 ms, authoritativenoyes / yesrefused-
b.ns.facebook.com 129.134.31.12NOERROR, 12 ms, authoritativenoyes / yesrefused-
b.ns.facebook.com 2a03:2880:f0fd:c:face:b00c:0:35NOERROR, 13 ms, authoritativenoyes / yesrefused-
c.ns.facebook.com 185.89.218.12NOERROR, 20 ms, authoritativenoyes / yesrefused-
c.ns.facebook.com 2a03:2880:f1fc:c:face:b00c:0:35NOERROR, 15 ms, authoritativenoyes / yesrefused-
d.ns.facebook.com 185.89.219.12NOERROR, 36 ms, authoritativenoyes / yesrefused-
d.ns.facebook.com 2a03:2880:f1fd:c:face:b00c:0:35NOERROR, 35 ms, authoritativenoyes / yesrefused-

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.
  • ✓ 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 4207849484 · primary a.ns.facebook.com

Found

Primary (MNAME)
a.ns.facebook.com
Contact (RNAME)
dns.facebook.com
Serial
4207849484
Refresh / retry
14400 s / 1800 s
Expire
604800 s
Negative TTL
3600 s

Serial per nameserver

NameserverSerial
a.ns.facebook.com (129.134.30.12)4207849484
a.ns.facebook.com (2a03:2880:f0fc:c:face:b00c:0:35)4207849484
b.ns.facebook.com (129.134.31.12)4207849484
b.ns.facebook.com (2a03:2880:f0fd:c:face:b00c:0:35)4207849484
c.ns.facebook.com (185.89.218.12)4207849484
c.ns.facebook.com (2a03:2880:f1fc:c:face:b00c:0:35)4207849484
d.ns.facebook.com (185.89.219.12)4207849484
d.ns.facebook.com (2a03:2880:f1fd:c:face:b00c:0:35)4207849484

Checks

  • ✓ Serial 4207849484 everywhere #22
    All nameservers serve the same version of the zone.
  • ✓ Timers within recommendations #23
    SOA refresh 4h, retry 30m, expire 7d, negative TTL 1h.
  • ✓ Primary is a public nameserver #24
    The primary nameserver a.ns.facebook.com is one of the listed nameservers.
  • ✓ Contact dns@facebook.com #25
    The SOA RNAME dns.facebook.com means dns@facebook.com.
  • ✓ Timestamp serial #26
    The serial 4207849484 is a Unix timestamp (2103-05-05 23:04 UTC).

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

8 records at the apex

Found

Read from
129.134.30.12:53
TypeValueTTL
SOAa.ns.facebook.com. dns.facebook.com. 4207849484 14400 1800 604800 36003600
NSc.ns.facebook.com.172800
NSa.ns.facebook.com.172800
NSb.ns.facebook.com.172800
NSd.ns.facebook.com.172800
A57.144.244.14160
AAAA2a03:2880:f37a:8d:face:b00c:0:260
TXT"v=spf1 -all"7200

Checks

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