bstpoc.serviceconnect.defence.gov.au
Updated:
2024-01-05 04:08:42 UTC (about a year ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (3)
- azure.com/SOA
- bstpoc.serviceconnect.defence.gov.au/CNAME
- npserviceconnectappgw.australiacentral.cloudapp.azure.com/A
Secure (2)
- com/SOA
- gov.au/SOA
DNSKEY/DS/NSEC status
Secure (15)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 30903)
- ./DNSKEY (alg 8, id 46780)
- NSEC3 proving non-existence of azure.com/DS
- 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)
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 46171)
- com/DS (alg 13, id 19718)
- 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 (3)
- azure.com to australiacentral.cloudapp.azure.com
- com to azure.com
- gov.au to defence.gov.au
Secure (3)
- . to au
- . to com
- au to gov.au
Notices
Errors (2)
- 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.
Warnings (3)
- 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.
- com to azure.com: Authoritative AAAA records exist for ns1-39.azure-dns.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
