equifax.com
Updated:
2021-05-06 19:09:18 UTC (1298 days ago)
Go to most recent »
Notices
DNSSEC Authentication Chain
RRset status
Insecure (5)
- equifax.com/A
- equifax.com/MX
- equifax.com/NS
- equifax.com/SOA
- equifax.com/TXT
Secure (2)
- com/SOA
- com/SOA
DNSKEY/DS/NSEC status
Secure (6)
- ./DNSKEY (alg 8, id 14631)
- ./DNSKEY (alg 8, id 20326)
- NSEC3 proving non-existence of equifax.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 equifax.com
Secure (1)
- . to com
Notices
Errors (16)
- equifax.com/DNSKEY: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (156.154.65.105, 2610:a1:1015::8d, UDP_-_NOEDNS_)
- equifax.com/DNSKEY: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (156.154.64.105, 156.154.65.105, 156.154.66.105, 2001:502:f3ff::8d, 2610:a1:1014::8d, 2610:a1:1015::8d, UDP_-_EDNS0_512_D_KN)
- equifax.com/DNSKEY: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (156.154.66.105, UDP_-_EDNS0_4096_D_N)
- equifax.com/MX: No response was received from the server over TCP (tried 1 times). See RFC 1035, Sec. 4.2. (2610:a1:1015::8d, TCP_-_EDNS0_4096_D_KN)
- equifax.com/MX: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (156.154.64.105, UDP_-_NOEDNS_)
- equifax.com/MX: No response was received from the server over UDP (tried 4 times). See RFC 1035, Sec. 4.2. (156.154.64.105, 156.154.65.105, 156.154.67.105, 2001:502:f3ff::8d, 2610:a1:1014::8d, 2610:a1:1015::8d, UDP_-_EDNS0_512_D_KN)
- equifax.com/MX: The UDP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (156.154.66.105, UDP_-_EDNS0_4096_D_KN)
- equifax.com/SOA: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (156.154.67.105, 2610:a1:1015::8d, UDP_-_NOEDNS_)
- equifax.com/SOA: No response was received from the server over UDP (tried 14 times). See RFC 1035, Sec. 4.2. (156.154.66.105, UDP_-_EDNS0_4096_D)
- equifax.com/SOA: The TCP connection was refused (ECONNREFUSED). See RFC 1035, Sec. 4.2. (156.154.66.105, TCP_-_EDNS0_4096_D_N)
- equifax.com/TXT: No response was received from the server over TCP (tried 3 times). See RFC 1035, Sec. 4.2. (2610:a1:1015::8d, TCP_-_EDNS0_4096_)
- equifax.com/TXT: No response was received from the server over UDP (tried 12 times). See RFC 1035, Sec. 4.2. (156.154.65.105, 156.154.67.105, UDP_-_NOEDNS_)
- 1nz2g3aohu.equifax.com/A has errors; select the "Denial of existence" DNSSEC option to see them.
- equifax.com/CNAME has errors; select the "Denial of existence" DNSSEC option to see them.
- equifax.com/AAAA has errors; select the "Denial of existence" DNSSEC option to see them.
- equifax.com/DNSKEY has errors; select the "Denial of existence" DNSSEC option to see them.
Warnings (8)
- equifax.com/A: 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. (156.154.67.105, UDP_-_EDNS0_4096_D_KN)
- equifax.com/MX: 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. (2610:a1:1014::8d, UDP_-_EDNS0_4096_D_KN)
- equifax.com/NS: 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. (2001:502:f3ff::8d, UDP_-_EDNS0_4096_D_KN)
- equifax.com/SOA: No response was received from the server over UDP (tried 11 times) until EDNS was disabled (however, this server appeared to respond legitimately to other queries with EDNS enabled). See RFC 6891, Sec. 6.2.6. (156.154.64.105, 2001:502:f3ff::8d, UDP_-_EDNS0_4096_D_KN, UDP_-_EDNS0_4096_D_KN_0x20)
- equifax.com/SOA: 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. (156.154.67.105, 2610:a1:1014::8d, UDP_-_EDNS0_4096_D_KN)
- equifax.com/SOA: 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. (156.154.64.105, UDP_-_EDNS0_4096_D_KN)
- 1nz2g3aohu.equifax.com/A has warnings; select the "Denial of existence" DNSSEC option to see them.
- equifax.com/AAAA has warnings; select the "Denial of existence" DNSSEC option to see them.
JavaScript is required to make the graph below interactive.
