infoblox.com
Updated:
2024-01-02 12:40:21 UTC (329 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- infoblox.com/A
- infoblox.com/AAAA
- infoblox.com/MX
- infoblox.com/NS
- infoblox.com/NSEC3PARAM
- infoblox.com/SOA
- infoblox.com/TXT
DNSKEY/DS/NSEC status
Secure (12)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- ./DNSKEY (alg 8, id 46780)
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 46171)
- com/DS (alg 13, id 19718)
- infoblox.com/DNSKEY (alg 8, id 19551)
- infoblox.com/DNSKEY (alg 8, id 30033)
- infoblox.com/DNSKEY (alg 8, id 40885)
- infoblox.com/DS (alg 8, id 36172)
- infoblox.com/DS (alg 8, id 40885)
- infoblox.com/DS (alg 8, id 40885)
Non_existent (1)
- infoblox.com/DNSKEY (alg 8, id 36172)
Delegation status
Secure (2)
- . to com
- com to infoblox.com
Notices
Errors (12)
- infoblox.com zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (104.40.90.56)
- infoblox.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:550:2:3::183:211, 2001:550:2:3::183:212)
- infoblox.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:2:3::183:211, 2001:550:2:3::183:212, UDP_-_NOEDNS_)
- infoblox.com/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (104.40.90.56, UDP_-_EDNS0_4096_D_KN)
- infoblox.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (38.108.181.211, 38.108.181.212, UDP_-_EDNS0_512_D_KN)
- infoblox.com/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (38.108.181.211, 38.108.181.212, UDP_-_EDNS0_512_D_KN)
- infoblox.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:2:3::183:211, 2001:550:2:3::183:212, UDP_-_NOEDNS_)
- infoblox.com/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (104.40.90.56, TCP_-_EDNS0_4096_D_N)
- infoblox.com/TXT: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (104.40.90.56, TCP_-_EDNS0_4096_D_KN)
- infoblox.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- infoblox.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- tlxcnbwujg.infoblox.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- infoblox.com/DS (alg 8, id 36172): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- infoblox.com/DS (alg 8, id 36172): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- infoblox.com/DS (alg 8, id 36172): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- infoblox.com/DS (alg 8, id 36172): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- infoblox.com/DS (alg 8, id 40885): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- infoblox.com/DS (alg 8, id 40885): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- infoblox.com/DS (alg 8, id 40885): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- infoblox.com/DS (alg 8, id 40885): DS records with digest type 1 (SHA-1) are ignored when DS records with digest type 2 (SHA-256) exist in the same RRset. See RFC 4509, Sec. 3.
- infoblox.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- tlxcnbwujg.infoblox.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
