transmedia.net.id
Updated:
2020-04-11 18:56:43 UTC (1639 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- transmedia.net.id/A
- transmedia.net.id/AAAA
- transmedia.net.id/MX
- transmedia.net.id/NS
- transmedia.net.id/SOA
- transmedia.net.id/TXT
DNSKEY/DS/NSEC status
Secure (13)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 48903)
- id/DNSKEY (alg 8, id 22449)
- id/DNSKEY (alg 8, id 26887)
- id/DS (alg 8, id 26887)
- id/DS (alg 8, id 26887)
- net.id/DNSKEY (alg 10, id 21768)
- net.id/DNSKEY (alg 10, id 7070)
- net.id/DS (alg 10, id 21768)
- net.id/DS (alg 10, id 21768)
- transmedia.net.id/DNSKEY (alg 13, id 21560)
- transmedia.net.id/DNSKEY (alg 13, id 6872)
- transmedia.net.id/DS (alg 13, id 6872)
Delegation status
Secure (3)
- . to id
- id to net.id
- net.id to transmedia.net.id
Notices
Errors (3)
- transmedia.net.id zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (202.180.15.1, 2001:d68:15:acce:5500::1)
- transmedia.net.id/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (202.180.15.1, 2001:d68:15:acce:5500::1, UDP_-_NOEDNS_)
- transmedia.net.id/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (202.180.15.1, 2001:d68:15:acce:5500::1, UDP_-_NOEDNS_)
Warnings (16)
- RRSIG net.id/DNSKEY alg 10, id 21768: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG net.id/DNSKEY alg 10, id 21768: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG net.id/DNSKEY alg 10, id 7070: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG net.id/DNSKEY alg 10, id 7070: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- RRSIG transmedia.net.id/DS alg 10, id 7070: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
- id/DS (alg 8, id 26887): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- id/DS (alg 8, id 26887): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- id/DS (alg 8, id 26887): 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.
- id/DS (alg 8, id 26887): 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.
- net.id to transmedia.net.id: The glue address(es) for nx1.transmedia.net.id (2001:d68:15:acce:5500::1) differed from its authoritative address(es) (2001:d68:3:8759:acce::1). See RFC 1034, Sec. 4.2.2.
- net.id to transmedia.net.id: The glue address(es) for nx1.transmedia.net.id (202.180.15.1) differed from its authoritative address(es) (202.180.8.1). See RFC 1034, Sec. 4.2.2.
- net.id/DS (alg 10, id 21768): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- net.id/DS (alg 10, id 21768): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- net.id/DS (alg 10, id 21768): 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.
- net.id/DS (alg 10, id 21768): 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.
- transmedia.net.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
