bssn.go.id

Updated: 2023-06-11 12:55:36 UTC (2 years ago) Go to most recent »

DNSSEC options (hide)

|?| RR types:
|?| DNSSEC algorithms:
|?| DS digest algorithms:
|?| Denial of existence:
|?| Redundant edges:
|?| Ignore RFC 8624:
|?| Ignore RFC 9276:
|?| Multi-signer:
|?| Trust anchors:
- Root zone KSK
|?| Additional trusted keys:

Notices

DNSSEC Authentication Chain

RRset status

Secure (6)

bssn.go.id/A
bssn.go.id/MX
bssn.go.id/NS
bssn.go.id/NSEC3PARAM
bssn.go.id/SOA
bssn.go.id/TXT

DNSKEY/DS/NSEC status

Secure (15)

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 60955)
bssn.go.id/DNSKEY (alg 7, id 22779)
bssn.go.id/DNSKEY (alg 7, id 25415)
bssn.go.id/DS (alg 7, id 12639)
bssn.go.id/DS (alg 7, id 20931)
bssn.go.id/DS (alg 7, id 22779)
bssn.go.id/DS (alg 7, id 48675)
bssn.go.id/DS (alg 7, id 50775)
go.id/DNSKEY (alg 10, id 25427)
go.id/DNSKEY (alg 10, id 48051)
go.id/DS (alg 10, id 48051)
id/DNSKEY (alg 8, id 22449)
id/DNSKEY (alg 8, id 26887)
id/DS (alg 8, id 26887)

Non_existent (4)

bssn.go.id/DNSKEY (alg 7, id 12639)
bssn.go.id/DNSKEY (alg 7, id 20931)
bssn.go.id/DNSKEY (alg 7, id 48675)
bssn.go.id/DNSKEY (alg 7, id 50775)

Delegation status

Secure (3)

. to id
go.id to bssn.go.id
id to go.id

Notices

Errors (5)

go.id zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (45.126.57.57)
go.id/DNSKEY: No response was received from the server over TCP (tried 12 times). See RFC 1035, Sec. 4.2. (45.126.57.57, TCP_-_EDNS0_4096_D_KN)
bssn.go.id/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
bssn.go.id/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
sw12izntdp.bssn.go.id/A has errors; select the "Denial of existence" DNSSEC option to see them.

Warnings (36)

RRSIG bssn.go.id/A alg 7, id 25415: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DNSKEY alg 7, id 22779: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DNSKEY alg 7, id 22779: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DNSKEY alg 7, id 25415: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DNSKEY alg 7, id 25415: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/DS alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/MX alg 7, id 25415: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/NS alg 7, id 25415: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/NSEC3PARAM alg 7, id 25415: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/SOA alg 7, id 25415: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG bssn.go.id/TXT alg 7, id 25415: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 10 (RSASHA512). See RFC 8624, Sec. 3.1.
bssn.go.id/DS (alg 7, id 12639): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 12639): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 20931): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 20931): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 22779): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 22779): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 48675): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 48675): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 50775): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
bssn.go.id/DS (alg 7, id 50775): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
id/DNSKEY (alg 8, id 22449): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:df5:4000:4::4, UDP_-_EDNS0_4096_D_KN)
id/DNSKEY (alg 8, id 26887): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (2001:df5:4000:4::4, UDP_-_EDNS0_4096_D_KN)
bssn.go.id/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
bssn.go.id/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
bssn.go.id/DS has warnings; select the "Denial of existence" DNSSEC option to see them.
bssn.go.id/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
sw12izntdp.bssn.go.id/A has warnings; select the "Denial of existence" DNSSEC option to see them.