maritim.go.id

Updated: 2023-11-17 08:40:21 UTC (154 days ago) Update now

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46780)
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)
maritim.go.id/DNSKEY (alg 13, id 2371)
maritim.go.id/DNSKEY (alg 13, id 34505)
maritim.go.id/DS (alg 13, id 2371)
maritim.go.id/DS (alg 13, id 44813)

go.id zone: The server(s) were not responsive to queries over TCP. (45.126.57.57)
go.id/DNSKEY: No response was received from the server over TCP (tried 12 times). (45.126.57.57, TCP_-_EDNS0_4096_D_KN)

RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
RRSIG go.id/DNSKEY alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
RRSIG go.id/DNSKEY alg 10, id 48051: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
RRSIG maritim.go.id/DS alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
RRSIG maritim.go.id/DS alg 10, id 25427: DNSSEC specification recommends not signing with DNSSEC algorithm 10 (RSASHA512).
go.id/DNSKEY (alg 10, id 25427): 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. (2402:ee80:d::d, UDP_-_EDNS0_4096_D_KN)
go.id/DNSKEY (alg 10, id 48051): 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. (2402:ee80:d::d, UDP_-_EDNS0_4096_D_KN)