fox.com
Updated:
2023-06-26 16:48:57 UTC (513 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Secure (6)
- fox.com/A
- fox.com/A
- fox.com/MX
- fox.com/NS
- fox.com/SOA
- fox.com/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 11019)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 46551)
- com/DS (alg 8, id 30909)
- fox.com/DNSKEY (alg 13, id 44688)
- fox.com/DNSKEY (alg 13, id 48553)
- fox.com/DNSKEY (alg 13, id 51997)
- fox.com/DS (alg 13, id 48553)
Delegation status
Secure (2)
- . to com
- com to fox.com
Notices
Errors (12)
- RRSIG fox.com/NS alg 13, id 44688: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 44688: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 44688: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 44688: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 51997: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 51997: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 51997: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 51997: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 51997: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 51997: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 51997: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 51997: With a TTL of 86400 the RRSIG RR can be in the cache of a non-validating resolver until 1 second after it expires at 2023-06-27 16:48:56+00:00. See RFC 4035, Sec. 5.3.3.
Warnings (4)
- com to fox.com: AAAA glue records exist for ns01.foxdoua.com, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- com to fox.com: AAAA glue records exist for ns02.foxdoua.com, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- com to fox.com: AAAA glue records exist for ns03.foxdoua.com, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
- com to fox.com: AAAA glue records exist for ns04.foxdoua.com, but there are no corresponding authoritative AAAA records. See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
