ups.com
Updated:
2026-02-11 14:28:27 UTC (23 days ago)
Update now
Notices
DNSSEC Authentication Chain
RRset status
Secure (7)
- ups.com/A
- ups.com/MX
- ups.com/NS
- ups.com/NSEC3PARAM
- ups.com/SOA
- ups.com/SOA
- ups.com/TXT
DNSKEY/DS/NSEC status
Secure (10)
- ./DNSKEY (alg 8, id 20326)
- ./DNSKEY (alg 8, id 21831)
- ./DNSKEY (alg 8, id 38696)
- com/DNSKEY (alg 13, id 19718)
- com/DNSKEY (alg 13, id 35511)
- com/DS (alg 13, id 19718)
- ups.com/DNSKEY (alg 8, id 30486)
- ups.com/DNSKEY (alg 8, id 42940)
- ups.com/DNSKEY (alg 8, id 63691)
- ups.com/DS (alg 8, id 63691)
Delegation status
Secure (2)
- . to com
- com to ups.com
Notices
Errors (21)
- RRSIG ups.com/DNSKEY alg 8, id 42940: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 4 hours, 34 minutes after it expires at 2026-02-13 09:54:19+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG ups.com/DNSKEY alg 8, id 42940: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 4 hours, 34 minutes after it expires at 2026-02-13 09:54:19+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG ups.com/DNSKEY alg 8, id 42940: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 4 hours, 34 minutes after it expires at 2026-02-13 09:54:19+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG ups.com/DNSKEY alg 8, id 63691: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 4 hours, 34 minutes after it expires at 2026-02-13 09:54:19+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG ups.com/DNSKEY alg 8, id 63691: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 4 hours, 34 minutes after it expires at 2026-02-13 09:54:19+00:00. See RFC 4035, Sec. 5.3.3.
- RRSIG ups.com/DNSKEY alg 8, id 63691: With a TTL of 172800 the RRSIG RR can be in the cache of a non-validating resolver until 4 hours, 34 minutes after it expires at 2026-02-13 09:54:19+00:00. See RFC 4035, Sec. 5.3.3.
- ups.com zone: The server(s) were not responsive to queries over UDP. See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d)
- ups.com/A: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, UDP_-_NOEDNS_)
- ups.com/DNSKEY: No response was received from the server over UDP (tried 11 times). See RFC 1035, Sec. 4.2. (153.2.244.155, UDP_-_EDNS0_4096_D)
- ups.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (153.2.242.115, 153.2.244.155, UDP_-_EDNS0_512_D_KN)
- ups.com/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (153.2.244.155, UDP_-_NOEDNS_)
- ups.com/NS: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (2001:550:1:a::d, 2001:550:1:b::d, UDP_-_NOEDNS_)
- ups.com/NSEC3PARAM: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (153.2.242.115, 153.2.244.155, UDP_-_NOEDNS_)
- ups.com/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (153.2.242.115, 153.2.244.155, UDP_-_NOEDNS_, UDP_-_NOEDNS__0x20)
- ups.com/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (153.2.242.115, 153.2.244.155, UDP_-_NOEDNS_)
- mcztd.q3p6b.ups.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
- ups.com/CDS has errors; select the "Denial of existence" DNSSEC option to see them.
- ups.com/CDNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
- ups.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- ups.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- ups.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (10)
- com to ups.com: Authoritative AAAA records exist for auth2.dns.cogentco.com, but there are no corresponding AAAA glue records. See RFC 1034, Sec. 4.2.2.
- ups.com/DNSKEY (alg 8, id 30486): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (153.2.242.115, UDP_-_EDNS0_4096_D_KN)
- ups.com/DNSKEY (alg 8, id 42940): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (153.2.242.115, UDP_-_EDNS0_4096_D_KN)
- ups.com/DNSKEY (alg 8, id 63691): No response was received until the UDP payload size was decreased, indicating that the server might be attempting to send a payload that exceeds the path maximum transmission unit (PMTU) size. See RFC 6891, Sec. 6.2.6. (153.2.242.115, UDP_-_EDNS0_4096_D_KN)
- mcztd.q3p6b.ups.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- ups.com/CDS has warnings; select the "Denial of existence" DNSSEC option to see them.
- ups.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
- ups.com/CDNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
- ups.com/CNAME has warnings; select the "Denial of existence" DNSSEC option to see them.
- ups.com/DNSKEY has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
