dev.digital.iag.com.au
Updated:
2023-07-27 14:12:59 UTC (514 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (4)
- dev.digital.iag.com.au/A (NODATA)
- dev.digital.iag.com.au/AAAA (NODATA)
- dev.digital.iag.com.au/CAA (NODATA)
- iag.com.au/SOA
Secure (1)
- com.au/SOA
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of iag.com.au/DS
- au/DNSKEY (alg 8, id 34882)
- au/DNSKEY (alg 8, id 5215)
- au/DS (alg 8, id 34882)
- com.au/DNSKEY (alg 8, id 12489)
- com.au/DNSKEY (alg 8, id 14185)
- com.au/DNSKEY (alg 8, id 61995)
- com.au/DS (alg 8, id 14185)
Delegation status
Insecure (1)
- com.au to iag.com.au
Secure (2)
- . to au
- au to com.au
Notices
Errors (3)
- NSEC3 proving non-existence of iag.com.au/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of iag.com.au/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- iag.com.au zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2.22.230.66)
Warnings (2)
- NSEC3 proving non-existence of iag.com.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of iag.com.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
JavaScript is required to make the graph below interactive.
