NSEC3 proving non-existence of myrams.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 myrams.com.au/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
securebanking.myrams.com.au zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (175.45.145.179, 175.45.152.11)
securebanking.myrams.com.au/MX has errors; select the "Denial of existence" DNSSEC option to see them.
securebanking.myrams.com.au/NS has errors; select the "Denial of existence" DNSSEC option to see them.
securebanking.myrams.com.au/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
securebanking.myrams.com.au/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
securebanking.myrams.com.au/NSEC3PARAM has errors; select the "Denial of existence" DNSSEC option to see them.
securebanking.myrams.com.au/SOA has errors; select the "Denial of existence" DNSSEC option to see them.
securebanking.myrams.com.au/TXT has errors; select the "Denial of existence" DNSSEC option to see them.
a968hfwcep.securebanking.myrams.com.au/A has errors; select the "Denial of existence" DNSSEC option to see them.
securebanking.myrams.com.au/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (2)
NSEC3 proving non-existence of myrams.com.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of myrams.com.au/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.