ampsers.com
Updated:
2021-05-25 11:38:24 UTC (4 years ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Insecure (9)
- ampsers.com/A
- ampsers.com/AAAA
- ampsers.com/MX
- ampsers.com/NS
- ampsers.com/NS
- ampsers.com/SOA
- ampsers.com/SOA
- ampsers.com/TXT
- ampsers.com/TXT (NODATA)
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Insecure (3)
- ampsers.com/DNSKEY (alg 13, id 2851)
- ampsers.com/DNSKEY (alg 13, id 46432)
- ampsers.com/DNSKEY (alg 13, id 61179)
Secure (6)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of ampsers.com/DS
- com/DNSKEY (alg 8, id 30909)
- com/DNSKEY (alg 8, id 54714)
- com/DS (alg 8, id 30909)
Delegation status
Insecure (1)
- com to ampsers.com
Secure (1)
- . to com
Notices
Errors (10)
- ampsers.com/A: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN)
- ampsers.com/AAAA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN)
- ampsers.com/DNSKEY (alg 13, id 2851): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- ampsers.com/MX: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- ampsers.com/NS: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN)
- ampsers.com/SOA: No RRSIG covering the RRset was returned in the response. See RFC 4035, Sec. 3.1.1. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN)
- ampsers.com/TXT (NODATA): No NSEC RR(s) were returned to validate the NODATA response. See RFC 4035, Sec. 3.1.3.1, RFC 5155, Sec. 7.2.3, RFC 5155, Sec. 7.2.4. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN)
- ampsers.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- ampsers.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- mj3thznsbd.ampsers.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (4)
- ampsers.com/DNSKEY (alg 13, id 46432): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- ampsers.com/DNSKEY (alg 13, id 61179): The DNSKEY RR was not found in the DNSKEY RRset returned by one or more servers. (205.251.193.16, 205.251.195.252, 205.251.196.197, 205.251.199.168, 2600:9000:5301:1000::1, 2600:9000:5303:fc00::1, 2600:9000:5304:c500::1, 2600:9000:5307:a800::1, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_512_D_KN)
- com to ampsers.com: Authoritative AAAA records exist for ns-116.awsdns-14.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- com to ampsers.com: Authoritative AAAA records exist for ns-272.awsdns-34.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
JavaScript is required to make the graph below interactive.
