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



X

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

Checked:
04.05.2021 09:47:59


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
questio.com.mx
A

yes
1
0

AAAA

yes


www.questio.com.mx

Name Error
yes
1
0
*.questio.com.mx
A
Name Error
yes



AAAA
Name Error
yes



CNAME
Name Error
yes



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 14631, Flags 256



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



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.05.2021, 00:00:00 +, Signature-Inception: 01.05.2021, 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: mx
mx
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 49357, DigestType 2 and Digest CSXnuoIb+iHYNcLnegKOo3el1FPe3CxIG158gLwbtk8=



1 RRSIG RR to validate DS RR found



RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 16.05.2021, 20:00:00 +, Signature-Inception: 03.05.2021, 19:00:00 +, KeyTag 14631, Signer-Name: (root)



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 36526, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 03.06.2021, 00:00:00 +, Signature-Inception: 04.05.2021, 00:00:00 +, KeyTag 36526, Signer-Name: mx



RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 01.07.2021, 15:00:00 +, Signature-Inception: 02.05.2021, 15:00:00 +, KeyTag 49357, Signer-Name: mx



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



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



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

Zone: com.mx
com.mx
1 DS RR in the parent zone found



DS with Algorithm 8, KeyTag 49357, DigestType 2 and Digest JOcJP+t51Mon7EDTzdwafHMuSXS6Kg/3DpIvsVBI0tA=



1 RRSIG RR to validate DS RR found



RRSIG-Owner com.mx., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 03.06.2021, 00:00:00 +, Signature-Inception: 04.05.2021, 00:00:00 +, KeyTag 36526, Signer-Name: mx



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 36526, Flags 256



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



2 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner com.mx., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 03.06.2021, 00:00:00 +, Signature-Inception: 04.05.2021, 00:00:00 +, KeyTag 36526, Signer-Name: com.mx



RRSIG-Owner com.mx., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 01.07.2021, 15:00:00 +, Signature-Inception: 02.05.2021, 15:00:00 +, KeyTag 49357, Signer-Name: com.mx



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



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



Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 49357, DigestType 2 and Digest "JOcJP+t51Mon7EDTzdwafHMuSXS6Kg/3DpIvsVBI0tA=" validates local Key with the same values, Key ist Secure Entry Point (SEP) of the zone

Zone: questio.com.mx
questio.com.mx
0 DS RR in the parent zone found



DS-Query in the parent zone has a valid NSEC3 RR as result with the hashed query name "gidr3riecrmghrd4afaruu3762psd8d4" between the hashed NSEC3-owner "gich57nrbf2afving3riv1c9ohd9cuca" and the hashed NextOwner "giihb855dimu4e8kr50q4js0sncfp54v". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner gich57nrbf2afving3riv1c9ohd9cuca.com.mx., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 03.06.2021, 00:00:00 +, Signature-Inception: 04.05.2021, 00:00:00 +, KeyTag 36526, Signer-Name: com.mx



DS-Query in the parent zone sends valid NSEC3 RR with the Hash "r8i9ol2dafeuda8k5bpm9qft77327lme" as Owner. That's the Hash of "com.mx" with the NextHashedOwnerName "r8ih3lroq82l3cb3tuk6ja42c5qh31p4". So that domain name is the Closest Encloser of "questio.com.mx". Opt-Out: True.
Bitmap: NS, SOA, RRSIG, DNSKEY, NSEC3PARAM Validated: RRSIG-Owner r8i9ol2dafeuda8k5bpm9qft77327lme.com.mx., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 03.06.2021, 00:00:00 +, Signature-Inception: 04.05.2021, 00:00:00 +, KeyTag 36526, Signer-Name: com.mx



0 DNSKEY RR found




Zone: www.questio.com.mx
www.questio.com.mx
0 DS RR in the parent zone found


3. Name Servers

DomainNameserverNS-IP
www.questio.com.mx
  ns1.digitalocean.com

questio.com.mx
  ns1.digitalocean.com / 67m39
173.245.58.51
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3a33
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns2.digitalocean.com / 67m28
173.245.59.41
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::adf5:3b29
Columbus/North Carolina/United States (US) - CLOUDFLARE


  ns3.digitalocean.com / 67m28
198.41.222.173
Chicago/Illinois/United States (US) - Cloudflare, Inc.


 
2400:cb00:2049:1::c629:dead
Columbus/North Carolina/United States (US) - CLOUDFLARE

com.mx
  c.mx-ns.mx
192.100.224.1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México S.C.


 
2001:1258::1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México S.C.


  e.mx-ns.mx / 2.ber.pch
189.201.244.1
Monterrey/Nuevo León/Mexico (MX) - WoodyNet


  i.mx-ns.mx / TLD_Host2.Amsterdam_Node1
207.248.68.1
Monterrey/Nuevo León/Mexico (MX) - NeuStar, Inc.


  m.mx-ns.mx
200.94.176.1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México S.C.


 
2001:13c7:7000::1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México S.C.


  o.mx-ns.mx
200.23.1.1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México S.C.


  x.mx-ns.mx / TLD_Host2.Frankfurt_Node1
201.131.252.1
Monterrey/Nuevo León/Mexico (MX) - NeuStar, Inc.

mx
  c.mx-ns.mx


  e.mx-ns.mx / 2.ber.pch


  i.mx-ns.mx / TLD_Host1.Amsterdam_Node1


  m.mx-ns.mx


  o.mx-ns.mx


  x.mx-ns.mx / TLD_Host1.Frankfurt_Node1


4. SOA-Entries


Domain:mx
Zone-Name:mx
Primary:m.mx-ns.mx
Mail:hostmaster.nic.mx
Serial:1620113711
Refresh:900
Retry:900
Expire:604800
TTL:1800
num Entries:6


Domain:com.mx
Zone-Name:com.mx
Primary:m.mx-ns.mx
Mail:hostmaster.nic.mx
Serial:1620112909
Refresh:900
Retry:900
Expire:604800
TTL:1800
num Entries:2


Domain:com.mx
Zone-Name:com.mx
Primary:m.mx-ns.mx
Mail:hostmaster.nic.mx
Serial:1620113808
Refresh:900
Retry:900
Expire:604800
TTL:1800
num Entries:6


Domain:questio.com.mx
Zone-Name:questio.com.mx
Primary:ns1.digitalocean.com
Mail:hostmaster.questio.com.mx
Serial:1620112019
Refresh:10800
Retry:3600
Expire:604800
TTL:1800
num Entries:6


Domain:www.questio.com.mx
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 "questio.com.mx" is domain, public suffix is ".com.mx", top-level-domain is ".mx", top-level-domain-type is "country-code", Country is Mexico, tld-manager is "NIC-Mexico ITESM - Campus Monterrey", num .mx-domains preloaded: 233 (complete: 151507)
Agood: No asked Authoritative Name Server had a timeout
ADNS: "Name Error" means: No www-dns-entry defined. This isn't a problem
HSTS-Preload-Status: unknown. Domain never included in the Preload-list. Check https://hstspreload.org/ to learn some basics about the Google-Preload-List.

2. DNS- and NameServer - Checks

AInfo:: 10 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 3 Name Servers.
AInfo:: 10 Queries complete, 10 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Ok (4 - 8):: An average of 3.3 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 3 different Name Servers found: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 3 Name Servers included in Delegation: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 3 Name Servers included in 1 Zone definitions: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com, 1 Name Servers listed in SOA.Primary: ns1.digitalocean.com.
AGood: Only one SOA.Primary Name Server found.: ns1.digitalocean.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.digitalocean.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: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.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: 3 different Name Servers found
AGood: All name servers have ipv4- and ipv6-addresses.: 3 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.: 3 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: digitalocean.com
Warning: All Name Servers from the same Country / IP location.: 3 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 3 Name Servers, 2 different subnets (first Byte): 173., 198., 2 different subnets (first two Bytes): 173.245., 198.41., 3 different subnets (first three Bytes): 173.245.58., 173.245.59., 198.41.222.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 3 Name Servers with IPv6, 1 different subnets (first block): 2400:, 1 different subnets (first two blocks): 2400:cb00:, 1 different subnets (first three blocks): 2400:cb00:2049:, 1 different subnets (first four blocks): 2400:cb00:2049:0001:
Fatal: All Name Server IPv6 addresses from the same subnet.
AGood: Nameserver supports TCP connections: 6 good Nameserver
AGood: Nameserver supports Echo Capitalization: 6 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 6 good Nameserver
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 6 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.digitalocean.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.
Nameserver doesn't pass all EDNS-Checks: x.mx-ns.mx: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: ok. NSID: ok (TLD_Host1.Frankfurt_Node1). COOKIE: ok. CLIENTSUBNET: ok.
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

AGood: Domainname is not on the "Specially Designated Nationals And Blocked Persons List" (SDN). That's an US-list of individuals and companies owned or controlled by, or acting for or on behalf of, targeted countries. It also lists individuals, groups, and entities, such as terrorists and narcotics traffickers designated under programs that are not country-specific. Collectively, such individuals and companies are called "Specially Designated Nationals" or "SDNs." Their assets are blocked and U.S. persons are generally prohibited from dealing with them. So if a domain name is on that list, it's impossible to create a Letsencrypt certificate with that domain name. Check the list manual - https://www.treasury.gov/resource-center/sanctions/sdn-list/pages/default.aspx
ADuration: 71036 milliseconds, 71.036 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: ns1.digitalocean.com, ns2.digitalocean.com, ns3.digitalocean.com

QNr.DomainTypeNS used
1
com
NS
b.root-servers.net (2001:500:200::b)

Answer: a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net, e.gtld-servers.net, f.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net, j.gtld-servers.net, k.gtld-servers.net, l.gtld-servers.net, m.gtld-servers.net
2
ns1.digitalocean.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: kim.ns.cloudflare.com, walt.ns.cloudflare.com

Answer: kim.ns.cloudflare.com
108.162.192.126, 172.64.32.126, 173.245.58.126, 2606:4700:50::adf5:3a7e, 2803:f800:50::6ca2:c07e, 2a06:98c1:50::ac40:207e

Answer: walt.ns.cloudflare.com
108.162.193.148, 172.64.33.148, 173.245.59.148, 2606:4700:58::adf5:3b94, 2803:f800:50::6ca2:c194, 2a06:98c1:50::ac40:2194
3
ns2.digitalocean.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: kim.ns.cloudflare.com, walt.ns.cloudflare.com

Answer: kim.ns.cloudflare.com
108.162.192.126, 172.64.32.126, 173.245.58.126, 2606:4700:50::adf5:3a7e, 2803:f800:50::6ca2:c07e, 2a06:98c1:50::ac40:207e

Answer: walt.ns.cloudflare.com
108.162.193.148, 172.64.33.148, 173.245.59.148, 2606:4700:58::adf5:3b94, 2803:f800:50::6ca2:c194, 2a06:98c1:50::ac40:2194
4
ns3.digitalocean.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: kim.ns.cloudflare.com, walt.ns.cloudflare.com

Answer: kim.ns.cloudflare.com
108.162.192.126, 172.64.32.126, 173.245.58.126, 2606:4700:50::adf5:3a7e, 2803:f800:50::6ca2:c07e, 2a06:98c1:50::ac40:207e

Answer: walt.ns.cloudflare.com
108.162.193.148, 172.64.33.148, 173.245.59.148, 2606:4700:58::adf5:3b94, 2803:f800:50::6ca2:c194, 2a06:98c1:50::ac40:2194
5
ns1.digitalocean.com: 173.245.58.51
A
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
6
ns1.digitalocean.com: 2400:cb00:2049:1::adf5:3a33
AAAA
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
7
ns2.digitalocean.com: 173.245.59.41
A
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
8
ns2.digitalocean.com: 2400:cb00:2049:1::adf5:3b29
AAAA
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
9
ns3.digitalocean.com: 198.41.222.173
A
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)
10
ns3.digitalocean.com: 2400:cb00:2049:1::c629:dead
AAAA
kim.ns.cloudflare.com (2606:4700:50::adf5:3a7e)


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
questio.com.mx
0

no CAA entry found
1
0
com.mx
0

no CAA entry found
1
0
mx
0

no CAA entry found
1
0


14. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
questio.com.mx

ok
1
0
_acme-challenge.questio.com.mx

Name Error - The domain name does not exist
1
0
_acme-challenge.questio.com.mx.questio.com.mx

Name Error - The domain name does not exist
1
0


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=b7234216-952a-47d8-9509-adf88075cba3


Last Result: https://check-your-website.server-daten.de/?q=questio.com.mx - 2021-05-04 09:47:59


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

<a href="https://check-your-website.server-daten.de/?q=questio.com.mx" target="_blank">Check this Site: questio.com.mx</a>