bstpoc.serviceconnect.defence.gov.au
Updated:
2024-01-05 00:02:05 UTC (about a year ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (1)
- gov.au/SOA
DNSKEY/DS/NSEC status
Secure (11)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of defence.gov.au/DS
- au/DNSKEY (alg 8, id 12570)
- au/DNSKEY (alg 8, id 51895)
- au/DS (alg 8, id 51895)
- gov.au/DNSKEY (alg 8, id 2222)
- gov.au/DNSKEY (alg 8, id 53715)
- gov.au/DNSKEY (alg 8, id 61269)
- gov.au/DS (alg 8, id 2222)
Delegation status
Insecure (1)
- gov.au to defence.gov.au
Secure (2)
- . to au
- au to gov.au
Notices
Errors (4)
- NSEC3 proving non-existence of defence.gov.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 defence.gov.au/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
- bstpoc.serviceconnect.defence.gov.au/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (203.6.66.1, 203.6.74.1, UDP_-_NOEDNS_)
- bstpoc.serviceconnect.defence.gov.au/AAAA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (203.6.66.1, 203.6.74.1, UDP_-_NOEDNS_)
Warnings (2)
- NSEC3 proving non-existence of defence.gov.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
- NSEC3 proving non-existence of defence.gov.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.
