citas.sre.gob.mx

Updated: 2022-11-16 10:51:15 UTC (767 days ago) Update now

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 18733)
./DNSKEY (alg 8, id 20326)
NSEC3 proving non-existence of sre.gob.mx/DS
gob.mx/DNSKEY (alg 8, id 17521)
gob.mx/DNSKEY (alg 8, id 61885)
gob.mx/DS (alg 8, id 61885)
incapdns.net/DNSKEY (alg 8, id 11284)
incapdns.net/DNSKEY (alg 8, id 21096)
incapdns.net/DS (alg 8, id 11284)
incapdns.net/DS (alg 8, id 11284)
mx/DNSKEY (alg 8, id 17521)
mx/DNSKEY (alg 8, id 61885)
mx/DS (alg 8, id 61885)
net/DNSKEY (alg 8, id 35886)
net/DNSKEY (alg 8, id 57635)
net/DS (alg 8, id 35886)

NSEC3 proving non-existence of sre.gob.mx/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 sre.gob.mx/DS: An iterations count of 0 must be used in NSEC3 records to alleviate computational burdens. See RFC 9276, Sec. 3.1.
sre.gob.mx zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (200.33.160.51)

NSEC3 proving non-existence of sre.gob.mx/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
NSEC3 proving non-existence of sre.gob.mx/DS: The salt value for an NSEC3 record should be empty. See RFC 9276, Sec. 3.1.
incapdns.net/DS (alg 8, id 11284): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
incapdns.net/DS (alg 8, id 11284): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
incapdns.net/DS (alg 8, id 11284): 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.
incapdns.net/DS (alg 8, id 11284): 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.