www.af.mil
Updated:
2023-05-23 08:18:21 UTC (910 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (9)
- akamaiedge.net/SOA
- e11218.dscb.akamaiedge.net.0.1.cn.akamaiedge.net/A
- e11218.dscb.akamaiedge.net.0.1.cn.akamaiedge.net/A
- e11218.dscb.akamaiedge.net.0.1.cn.akamaiedge.net/AAAA
- e11218.dscb.akamaiedge.net/A
- e11218.dscb.akamaiedge.net/A
- e11218.dscb.akamaiedge.net/AAAA
- e11218.dscb.akamaiedge.net/CNAME
- www.afpw.af.mil.edgekey.net/CNAME
Secure (4)
- net/SOA
- net/SOA
- net/SOA
- www.af.mil/CNAME
DNSKEY/DS/NSEC status
Secure (16)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 60955)
- NSEC3 proving non-existence of akamaiedge.net/DS
- NSEC3 proving non-existence of edgekey.net/DS
- af.mil/DNSKEY (alg 8, id 15258)
- af.mil/DNSKEY (alg 8, id 2725)
- af.mil/DNSKEY (alg 8, id 495)
- af.mil/DS (alg 8, id 2725)
- af.mil/DS (alg 8, id 2725)
- mil/DNSKEY (alg 8, id 1773)
- mil/DNSKEY (alg 8, id 40318)
- mil/DNSKEY (alg 8, id 62470)
- mil/DS (alg 8, id 62470)
- net/DNSKEY (alg 8, id 27554)
- net/DNSKEY (alg 8, id 35886)
- net/DS (alg 8, id 35886)
Delegation status
Insecure (4)
- akamaiedge.net to cn.akamaiedge.net
- akamaiedge.net to dscb.akamaiedge.net
- net to akamaiedge.net
- net to edgekey.net
Secure (3)
- . to mil
- . to net
- mil to af.mil
Notices
Errors (1)
- af.mil/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (32)
- af.mil/DS (alg 8, id 2725): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- af.mil/DS (alg 8, id 2725): DNSSEC implementers are prohibited from implementing signing with DS algorithm 1 (SHA-1). See RFC 8624, Sec. 3.2.
- af.mil/DS (alg 8, id 2725): 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.
- af.mil/DS (alg 8, id 2725): 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.
- akamaiedge.net to cn.akamaiedge.net: The glue address(es) for n1cn.akamaiedge.net (23.204.146.243, 184.51.100.5) differed from its authoritative address(es) (184.51.100.5). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to cn.akamaiedge.net: The glue address(es) for n1cn.akamaiedge.net (2600:140b:1:f000:f88b:dc72:9ccd:dcf8, 2a02:26f0:5c:f000:f31::) differed from its authoritative address(es) (2600:140b:1:f000:f88b:dc72:9ccd:dcf8). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to cn.akamaiedge.net: The glue address(es) for n2cn.akamaiedge.net (23.200.73.219, 23.205.154.55) differed from its authoritative address(es) (23.200.73.219). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to cn.akamaiedge.net: The glue address(es) for n3cn.akamaiedge.net (23.200.73.216, 23.205.154.53) differed from its authoritative address(es) (23.200.73.216). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to cn.akamaiedge.net: The glue address(es) for n4cn.akamaiedge.net (23.200.73.220, 23.205.154.48) differed from its authoritative address(es) (23.200.73.220). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to cn.akamaiedge.net: The glue address(es) for n5cn.akamaiedge.net (23.200.73.223, 23.205.154.49) differed from its authoritative address(es) (23.200.73.223). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to cn.akamaiedge.net: The glue address(es) for n6cn.akamaiedge.net (23.15.241.243, 23.200.73.218) differed from its authoritative address(es) (23.200.73.218). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to cn.akamaiedge.net: The glue address(es) for n7cn.akamaiedge.net (23.1.234.120, 184.25.56.9) differed from its authoritative address(es) (184.25.56.9). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (23.211.133.192, UDP_-_EDNS0_4096_D_KN)
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n1dscb.akamaiedge.net (23.15.241.52, 23.213.244.109) differed from its authoritative address(es) (23.213.244.109). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n2dscb.akamaiedge.net (23.15.240.222, 23.216.148.138) differed from its authoritative address(es) (23.216.148.138). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n3dscb.akamaiedge.net (23.15.240.133, 23.216.148.153) differed from its authoritative address(es) (23.216.148.153). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n4dscb.akamaiedge.net (23.15.240.198, 23.216.148.81) differed from its authoritative address(es) (23.216.148.81). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n5dscb.akamaiedge.net (23.15.240.220, 23.216.148.80) differed from its authoritative address(es) (23.216.148.80). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n6dscb.akamaiedge.net (23.216.148.77, 104.98.117.39) differed from its authoritative address(es) (23.216.148.77). See RFC 1034, Sec. 4.2.2.
- akamaiedge.net to dscb.akamaiedge.net: The glue address(es) for n7dscb.akamaiedge.net (23.1.237.84, 72.246.199.57) differed from its authoritative address(es) (72.246.199.57). See RFC 1034, Sec. 4.2.2.
- e11218.dscb.akamaiedge.net.0.1.cn.akamaiedge.net/AAAA: No response was received from the server over UDP (tried 10 times) until the DO EDNS flag was cleared (however, this server appeared to respond legitimately to other queries with the DO EDNS flag set). See RFC 6891, Sec. 6.1.4. (2a02:26f0:5c:f000:f31::, UDP_-_EDNS0_4096_D_KN)
- e11218.dscb.akamaiedge.net/CNAME: The server returned CNAME for e11218.dscb.akamaiedge.net, but records of other types exist at that name. See RFC 2181, Sec. 10.1.
- net to akamaiedge.net: Authoritative AAAA records exist for a11-192.akamaiedge.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: Authoritative AAAA records exist for a12-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: Authoritative AAAA records exist for a13-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: Authoritative AAAA records exist for a18-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: Authoritative AAAA records exist for a28-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: Authoritative AAAA records exist for a5-65.akam.net, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the net zone): a11-65.akam.net, ns1-2.akam.net, a9-65.akam.net, a3-65.akam.net See RFC 1034, Sec. 4.2.2.
- net to edgekey.net: The following NS name(s) were found in the delegation NS RRset (i.e., in the net zone), but not in the authoritative NS RRset: ns1-66.akam.net, ns4-66.akam.net, ns5-66.akam.net, ns7-65.akam.net See RFC 1034, Sec. 4.2.2.
- www.afpw.af.mil.edgekey.net/CNAME: No response was received from the server over UDP (tried 6 times) until the COOKIE EDNS option was removed (however, this server appeared to respond legitimately to other queries with the COOKIE EDNS option present). See RFC 6891, Sec. 6.1.2. (184.26.160.65, 2600:1408:1c::41, UDP_-_EDNS0_4096_D_KN)
- af.mil/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
