Check DNS, Urls + Redirects, Certificates and Content of your Website



X

DNS-problem - authoritative Nameserver refused, not defined or timeout

Checked:
14.05.2022 14:44:11


Older results


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
yahoo
A

yes
1
0

AAAA

yes


www.yahoo

Name Error
yes
1
0


2. DNSSEC

Zone (*)DNSSEC - Informations

Zone: (root)
(root)
1 DS RR published



DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest 4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=



Status: Valid because published



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 20326, Flags 257 (SEP = Secure Entry Point)



Public Key with Algorithm 8, KeyTag 47671, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 01.06.2022, 00:00:00 +, Signature-Inception: 11.05.2022, 00:00:00 +, KeyTag 20326, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 20326 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 20326, DigestType 2 and Digest "4G1EuAuPHTmpXAsNfGXQhFjogECbvGg0VxBCN8f47I0=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: yahoo
yahoo
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 52260, DigestType 2 and Digest mdpe1ZypT8jCjFx6SoF+f8DFJoixFdz3Q/uRS+ZbpEc=



1 RRSIG RR to validate DS RR found



RRSIG-Owner yahoo., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 27.05.2022, 05:00:00 +, Signature-Inception: 14.05.2022, 04:00:00 +, KeyTag 47671, Signer-Name: (root)



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 47671 used to validate the DS RRSet in the parent zone



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 733, Flags 256



Public Key with Algorithm 8, KeyTag 52260, Flags 257 (SEP = Secure Entry Point)



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner yahoo., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 19.05.2022, 14:41:02 +, Signature-Inception: 04.05.2022, 14:36:02 +, KeyTag 52260, Signer-Name: yahoo



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 52260 used to validate the DNSKEY RRSet



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 52260, DigestType 2 and Digest "mdpe1ZypT8jCjFx6SoF+f8DFJoixFdz3Q/uRS+ZbpEc=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone



A-Query sends a valid NSEC3 RR as result with the hashed owner name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" (unhashed: yahoo). So that's the Closest Encloser of the query name. A-Query sends a valid NSEC3 RR as result with the hashed query name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" equal the hashed NSEC3-owner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" and the hashed NextOwner "9okrp2d2vdemn6g4dhng6mlo6ub1441k". So the zone confirmes the not-existence of that A RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ocp0dtid5u0v97k8ra9bu2f54oid3ii7.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo



Status: Good. NoData-Proof required and found.



CNAME-Query sends a valid NSEC3 RR as result with the hashed owner name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" (unhashed: yahoo). So that's the Closest Encloser of the query name. CNAME-Query sends a valid NSEC3 RR as result with the hashed query name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" equal the hashed NSEC3-owner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" and the hashed NextOwner "9okrp2d2vdemn6g4dhng6mlo6ub1441k". So the zone confirmes the not-existence of that CNAME RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ocp0dtid5u0v97k8ra9bu2f54oid3ii7.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo



Status: Good. NoData-Proof required and found.



TXT-Query sends a valid NSEC3 RR as result with the hashed owner name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" (unhashed: yahoo). So that's the Closest Encloser of the query name. TXT-Query sends a valid NSEC3 RR as result with the hashed query name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" equal the hashed NSEC3-owner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" and the hashed NextOwner "9okrp2d2vdemn6g4dhng6mlo6ub1441k". So the zone confirmes the not-existence of that TXT RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ocp0dtid5u0v97k8ra9bu2f54oid3ii7.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo



Status: Good. NoData-Proof required and found.



AAAA-Query sends a valid NSEC3 RR as result with the hashed owner name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" (unhashed: yahoo). So that's the Closest Encloser of the query name. AAAA-Query sends a valid NSEC3 RR as result with the hashed query name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" equal the hashed NSEC3-owner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" and the hashed NextOwner "9okrp2d2vdemn6g4dhng6mlo6ub1441k". So the zone confirmes the not-existence of that AAAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ocp0dtid5u0v97k8ra9bu2f54oid3ii7.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo



Status: Good. NoData-Proof required and found.



TLSA-Query (_443._tcp.yahoo) sends a valid NSEC3 RR as result with the hashed owner name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" (unhashed: yahoo). So that's the Closest Encloser of the query name. TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Next Closer Name "t5v502l4rnigirch7kpv7r1nd4m42h94" (unhashed: _tcp.yahoo) with the owner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" and the NextOwner "9okrp2d2vdemn6g4dhng6mlo6ub1441k". So that NSEC3 confirms the not-existence of the Next Closer Name.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ocp0dtid5u0v97k8ra9bu2f54oid3ii7.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo



Status: Good. NXDomain-Proof required and found.



TLSA-Query sends a valid NSEC3 RR as result and covers the hashed Wildcard expansion of the ClosestEncloser "mtc2v6h96pc0in70lh753kf5a3g0h3ob" (unhashed: *.yahoo) with the owner "9okrp2d2vdemn6g4dhng6mlo6ub1441k" and the NextOwner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7". So that NSEC3 confirms the not-existence of the Wildcard expansion. TLSA-Query (_443._tcp.yahoo) sends a valid NSEC3 RR as result with the hashed query name "g717ugrjt4icpu79hsc7gugp5hk7uncv" between the hashed NSEC3-owner "9okrp2d2vdemn6g4dhng6mlo6ub1441k" and the hashed NextOwner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7". So the zone confirmes the not-existence of that TLSA RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 9okrp2d2vdemn6g4dhng6mlo6ub1441k.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo



Status: Good. NXDomain-Proof required and found.



CAA-Query sends a valid NSEC3 RR as result with the hashed owner name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" (unhashed: yahoo). So that's the Closest Encloser of the query name. CAA-Query sends a valid NSEC3 RR as result with the hashed query name "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" equal the hashed NSEC3-owner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" and the hashed NextOwner "9okrp2d2vdemn6g4dhng6mlo6ub1441k". So the zone confirmes the not-existence of that CAA RR, but the existence of that query name (minimal one RR with that name exists).
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ocp0dtid5u0v97k8ra9bu2f54oid3ii7.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo



Status: Good. NoData-Proof required and found.

Zone: www.yahoo
www.yahoo
0 DS RR in the parent zone found



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "ocp0dtid5u0v97k8ra9bu2f54oid3ii7" as Owner. That's the Hash of "yahoo" with the NextHashedOwnerName "9okrp2d2vdemn6g4dhng6mlo6ub1441k". So that domain name is the Closest Encloser of "www.yahoo". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner ocp0dtid5u0v97k8ra9bu2f54oid3ii7.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo



The ClosestEncloser says, that "*.yahoo" with the Hash "mtc2v6h96pc0in70lh753kf5a3g0h3ob" is a possible Wildcard of the DS Query Name. But the DS-Query in the parent zone sends a valid NSEC3 RR With the owner "9okrp2d2vdemn6g4dhng6mlo6ub1441k" and the Next Owner "ocp0dtid5u0v97k8ra9bu2f54oid3ii7", so the Hash of the wildcard is between these hashes. So that NSEC3 proves the Not-existence of that wildcard expansion. Opt-Out: True
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner 9okrp2d2vdemn6g4dhng6mlo6ub1441k.yahoo., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 20.05.2022, 03:20:17 +, Signature-Inception: 13.05.2022, 03:20:17 +, KeyTag 733, Signer-Name: yahoo


3. Name Servers

DomainNameserverNS-IP
www.yahoo
  ac1.nstld.com

yahoo
  ac1.nstld.com / nnn1-fra5
2001:500:120::30
Reston/Virginia/United States (US) - VeriSign Global Registry Services


  ac2.nstld.com / nnn1-nlams-1a
2001:500:121::30
Roubaix/Hauts-de-France/France (FR) - VeriSign Global Registry Services


  ac3.nstld.com / nnn1-fra6
2001:500:122::30
New York/United States (US) - VeriSign Global Registry Services


  ac4.nstld.com / nnn1-fra5
2001:500:123::30
New York/United States (US) - VeriSign Global Registry Services


4. SOA-Entries


Domain:yahoo
Zone-Name:yahoo
Primary:ac1.nstld.com
Mail:info.verisign-grs.com
Serial:1652532221
Refresh:1800
Retry:900
Expire:604800
TTL:86400
num Entries:4


Domain:www.yahoo
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


5. Screenshots

No Screenshot listed, because no url-check with https + http status 200-299, 400-599 + not-ACME-check found.

6. Url-Checks

DomainnameHttp-StatusredirectSec.G







7. Comments


1. General Results, most used to calculate the result

Aname "yahoo" is public suffix, public suffix is ".yahoo", top-level-domain is ".yahoo", top-level-domain-type is "generic", tld-manager is "Yahoo! Domain Services Inc.", num .yahoo-domains preloaded: 0 (complete: 175327)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem

2. DNS- and NameServer - Checks

AGood: Only one SOA.Primary Name Server found.: ac1.nstld.com.
AGood: SOA.Primary Name Server included in the delegation set.: ac1.nstld.com.
AGood: Consistency between delegation and zone. The set of NS records served by the authoritative name servers must match those proposed for the delegation in the parent zone. Ordered list of name servers: ac1.nstld.com, ac2.nstld.com, ac3.nstld.com, ac4.nstld.com
AGood: All Name Server Domain Names have a Public Suffix.
AGood: All Name Server Domain Names ending with a Public Suffix have minimal one IPv4- or IPv6 address.
AGood: All Name Server ip addresses are public.
AGood: Minimal 2 different name servers (public suffix and public ip address) found: 4 different Name Servers found
Warning: All Name Servers have the same Top Level Domain / Public Suffix. If there is a problem with that Top Level Domain, your domain may be affected. Better: Use Name Servers with different top level domains.: 4 Name Servers, 1 Top Level Domain: com
Warning: All Name Servers have the same domain name. If there is a problem with that domain name (or with the name servers of that domain name), your domain may be affected. Better: Use Name Servers with different domain names / different top level domains.: Only one domain name used: nstld.com
AGood: Name servers with different Country locations found: 4 Name Servers, 2 Countries: FR, US
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 4 good Nameserver
AGood: Nameserver supports Echo Capitalization: 4 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 4 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 4 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ac1.nstld.com: OP100: no result. FLAGS: no result. V1: no result. V1OP100: no result. V1FLAGS: no result. DNSSEC: no result. V1DNSSEC: no result. NSID: no result. COOKIE: no result. CLIENTSUBNET: no result.
AGood: All SOA have the same Serial Number
Warning: No CAA entry with issue/issuewild found, every CAA can create a certificate. Read https://en.wikipedia.org/wiki/DNS_Certification_Authority_Authorization to learn some basics about the idea of CAA. Your name server must support such an entry. Not all dns providers support CAA entries.

3. Content- and Performance-critical Checks

ADuration: 21433 milliseconds, 21.433 seconds


8. Connections

No connection informations found. Perhaps only http - connections.


9. Certificates

No certificate informations found. Perhaps only http - connections.


10. Last Certificates - Certificate Transparency Log Check

1. Source CertSpotter - active certificates (one check per day)

No CertSpotter - CT-Log entries found


2. Source crt.sh - old and new certificates, sometimes very slow - only certificates with "not after" > 2019 are listed

No CRT - CT-Log entries found


11. Html-Content - Entries

No Html-Content entries found. Only checked if https + status 200/401/403/404


12. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers:


No NameServer - IP address - Informations found


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
yahoo
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
_acme-challenge.yahoo

Name Error - The domain name does not exist
1
0
_acme-challenge.yahoo.yahoo

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=82a0912d-9bbc-48e6-b6f9-2b77a8c743fd


Last Result: https://check-your-website.server-daten.de/?q=yahoo%2fspawn77 - 2022-05-14 14:44:11


Do you like this page? Support this tool, add a link on your page:

<a href="https://check-your-website.server-daten.de/?q=yahoo%2fspawn77" target="_blank">Check this Site: yahoo/spawn77</a>