freedom.ne.jp
Updated:
2023-07-18 07:57:02 UTC (512 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (5)
- freedom.ne.jp/A
- freedom.ne.jp/MX
- freedom.ne.jp/NS
- freedom.ne.jp/SOA
- freedom.ne.jp/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- freedom.ne.jp/DNSKEY (alg 7, id 36536)
- freedom.ne.jp/DNSKEY (alg 7, id 54754)
- freedom.ne.jp/DS (alg 7, id 36536)
- freedom.ne.jp/DS (alg 7, id 36536)
- jp/DNSKEY (alg 8, id 2760)
- jp/DNSKEY (alg 8, id 39916)
- jp/DNSKEY (alg 8, id 53418)
- jp/DS (alg 8, id 39916)
Delegation status
Secure (2)
- . to jp
- jp to freedom.ne.jp
Notices
Errors (3)
- freedom.ne.jp zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (211.2.168.243)
- freedom.ne.jp/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (211.2.168.243, UDP_-_NOEDNS_)
- freedom.ne.jp/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (211.2.168.243, UDP_-_NOEDNS_)
Warnings (19)
- RRSIG freedom.ne.jp/A alg 7, id 54754: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG freedom.ne.jp/DNSKEY alg 7, id 36536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG freedom.ne.jp/DNSKEY alg 7, id 36536: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG freedom.ne.jp/DNSKEY alg 7, id 54754: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG freedom.ne.jp/DNSKEY alg 7, id 54754: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG freedom.ne.jp/MX alg 7, id 54754: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG freedom.ne.jp/NS alg 7, id 54754: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG freedom.ne.jp/SOA alg 7, id 54754: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- RRSIG freedom.ne.jp/TXT alg 7, id 54754: DNSSEC implementers are recommended against implementing signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1). See RFC 8624, Sec. 3.1.
- freedom.ne.jp/DS (alg 7, id 36536): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- freedom.ne.jp/DS (alg 7, id 36536): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- freedom.ne.jp/DS (alg 7, id 36536): 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.
- freedom.ne.jp/DS (alg 7, id 36536): 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.
- jp to freedom.ne.jp: The glue address(es) for ns1.freedom.ne.jp (202.211.116.2) differed from its authoritative address(es) (202.211.116.3). See RFC 1034, Sec. 4.2.2.
- freedom.ne.jp/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- freedom.ne.jp/NSEC3PARAM has warnings; select the "Denial of existence" DNSSEC option to see them.
- freedom.ne.jp/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- freedom.ne.jp/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- ra4ov9h3cf.freedom.ne.jp/A has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
