infoblox.com
Updated:
2024-02-09 16:43:46 UTC (232 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 (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 4534)
- com/DS (alg 13, id 19718)
- infoblox.com/DNSKEY (alg 8, id 25773)
- 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 (10)
- 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/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.
- uo1ag7er5t.infoblox.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (11)
- 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/NS: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (38.108.181.211, 38.108.181.212, UDP_-_EDNS0_4096_D_KN)
- infoblox.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- uo1ag7er5t.infoblox.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
