club1.fr

Updated: 2023-09-28 10:13:26 UTC (422 days ago) Go to most recent »

DNSSEC options (hide)

Notices

DNSSEC Authentication Chain

./DNSKEY (alg 8, id 11019)
./DNSKEY (alg 8, id 20326)
./DNSKEY (alg 8, id 46780)
NSEC3 proving non-existence of club1.fr/DS
fr/DNSKEY (alg 13, id 29133)
fr/DNSKEY (alg 13, id 60747)
fr/DS (alg 13, id 29133)

RRSIG club1.fr/A alg 13, id 8897: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2023-10-04 06:46:57+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG club1.fr/AAAA alg 13, id 8897: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2023-10-04 06:46:57+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG club1.fr/MX alg 13, id 8897: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2023-10-04 06:46:57+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG club1.fr/NS alg 13, id 8897: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2023-10-04 00:33:37+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG club1.fr/NS alg 13, id 8897: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2023-10-04 06:46:57+00:00. See RFC 4035, Sec. 5.3.3.
RRSIG club1.fr/TXT alg 13, id 8897: With a TTL of 604800 the RRSIG RR can be in the cache of a non-validating resolver until 1 day after it expires at 2023-10-04 06:46:57+00:00. See RFC 4035, Sec. 5.3.3.

fr to club1.fr: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the fr zone): ns1.he.net See RFC 1034, Sec. 4.2.2.