fox.com
Updated:
2025-03-14 01:36:21 UTC (338 days ago)
Update now
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 20326)
- ./DNSKEY (alg 8, id 26470)
- ./DNSKEY (alg 8, id 38696)
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 23202)
- com/DS (alg 13, id 19718)
- fox.com/DNSKEY (alg 13, id 12196)
- fox.com/DNSKEY (alg 13, id 48553)
- fox.com/DNSKEY (alg 13, id 52254)
- fox.com/DS (alg 13, id 48553)
Delegation status
Secure (2)
- . to com
- com to fox.com
Notices
Errors (13)
- RRSIG fox.com/NS alg 13, id 12196: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 12196: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 12196: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 12196: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 52254: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 52254: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 52254: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 52254: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 52254: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 52254: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 52254: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG fox.com/NS alg 13, id 52254: 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 2025-03-15 01:36:20+00:00. See RFC 4035, Sec. 5.3.3.
- com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (192.26.92.30, UDP_-_EDNS0_512_D_KN)
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.
