balug.org
Updated:
2024-06-07 00:59:28 UTC (169 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- balug.org/A
- balug.org/AAAA
- balug.org/MX
- balug.org/NS
- balug.org/SOA
- balug.org/TXT
DNSKEY/DS/NSEC status
Secure (9)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 5613)
- balug.org/DNSKEY (alg 8, id 17095)
- balug.org/DNSKEY (alg 8, id 42576)
- balug.org/DS (alg 8, id 17095)
- org/DNSKEY (alg 8, id 26974)
- org/DNSKEY (alg 8, id 3093)
- org/DNSKEY (alg 8, id 55149)
- org/DS (alg 8, id 26974)
Delegation status
Secure (2)
- . to org
- org to balug.org
Notices
Errors (5)
- balug.org zone: The server(s) were not responsive to queries over TCP. See RFC 1035, Sec. 4.2. (50.242.105.52)
- balug.org/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (50.242.105.52, UDP_-_EDNS0_512_D_KN)
- balug.org/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (50.242.105.52, UDP_-_EDNS0_512_D_KN)
- balug.org/SOA: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (50.242.105.52, TCP_-_EDNS0_4096_D_N)
- balug.org/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (1)
- balug.org/A: 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. (50.242.105.52, UDP_-_EDNS0_4096_D_KN)
JavaScript is required to make the graph below interactive.
