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



U

No dns entry found - perhaps mistype. Or wrong IDN

Checked:
08.04.2021 06:40:22


Older results

No older results found


1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
torneodeclubes2021powerade.com.mx

Name Error
yes
1
0
www.torneodeclubes2021powerade.com.mx

Name Error
yes
1
0
*.torneodeclubes2021powerade.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



3 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)



Public Key with Algorithm 8, KeyTag 42351, Flags 256



1 RRSIG RR to validate DNSKEY RR found



RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 22.04.2021, 00:00:00 +, Signature-Inception: 01.04.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: 20.04.2021, 17:00:00 +, Signature-Inception: 07.04.2021, 16: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 28776, 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: 07.05.2021, 00:00:00 +, Signature-Inception: 07.04.2021, 00:00:00 +, KeyTag 28776, Signer-Name: mx



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



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 28776 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: 07.05.2021, 00:00:00 +, Signature-Inception: 07.04.2021, 00:00:00 +, KeyTag 28776, Signer-Name: mx



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



2 DNSKEY RR found



Public Key with Algorithm 8, KeyTag 28776, 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: 07.05.2021, 00:00:00 +, Signature-Inception: 07.04.2021, 00:00:00 +, KeyTag 28776, Signer-Name: com.mx



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



Status: Good - Algorithmus 8 and DNSKEY with KeyTag 28776 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: torneodeclubes2021powerade.com.mx
torneodeclubes2021powerade.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 "rlf4sbngorhasdnqms49hos11oq96pa5" between the hashed NSEC3-owner "rlbsstsb7d5al4cs6amnhq9a42edqiku" and the hashed NextOwner "rlhaeavo7s1iueppo8jbtadubh8j0qqk". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner rlbsstsb7d5al4cs6amnhq9a42edqiku.com.mx., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 07.05.2021, 00:00:00 +, Signature-Inception: 07.04.2021, 00:00:00 +, KeyTag 28776, Signer-Name: com.mx



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



The ClosestEncloser says, that "*.com.mx" with the Hash "4j9fkrlecp1e9vk02rn6nejljai195ac" 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 "4j96v1sinusvnb1pa8n622m5pkiu0r2l" and the Next Owner "4jasje1po89vjvehqbhksfpqemupn3ub", 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 4j96v1sinusvnb1pa8n622m5pkiu0r2l.com.mx., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 07.05.2021, 00:00:00 +, Signature-Inception: 07.04.2021, 00:00:00 +, KeyTag 28776, Signer-Name: com.mx

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



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



The ClosestEncloser says, that "*.com.mx" with the Hash "4j9fkrlecp1e9vk02rn6nejljai195ac" 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 "4j96v1sinusvnb1pa8n622m5pkiu0r2l" and the Next Owner "4jasje1po89vjvehqbhksfpqemupn3ub", 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 4j96v1sinusvnb1pa8n622m5pkiu0r2l.com.mx., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 07.05.2021, 00:00:00 +, Signature-Inception: 07.04.2021, 00:00:00 +, KeyTag 28776, Signer-Name: com.mx


3. Name Servers

DomainNameserverNS-IP
www.torneodeclubes2021powerade.com.mx
  m.mx-ns.mx

torneodeclubes2021powerade.com.mx
  m.mx-ns.mx

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_Host1.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_Host1.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:1617855592
Refresh:900
Retry:900
Expire:604800
TTL:1800
num Entries:4


Domain:mx
Zone-Name:mx
Primary:m.mx-ns.mx
Mail:hostmaster.nic.mx
Serial:1617856492
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:1617855693
Refresh:900
Retry:900
Expire:604800
TTL:1800
num Entries:8


Domain:torneodeclubes2021powerade.com.mx
Zone-Name:
Primary:
Mail:
Serial:
Refresh:
Retry:
Expire:
TTL:
num Entries:1


Domain:www.torneodeclubes2021powerade.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 "torneodeclubes2021powerade.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:: 1 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 0 Name Servers.
AInfo:: 1 Queries complete, 1 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
AInfo:: 6 different Name Servers found: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx, 6 Name Servers included in Delegation: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx, 6 Name Servers included in 1 Zone definitions: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx, 1 Name Servers listed in SOA.Primary: m.mx-ns.mx.
AGood: Only one SOA.Primary Name Server found.: m.mx-ns.mx.
AGood: SOA.Primary Name Server included in the delegation set.: m.mx-ns.mx.
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.
AInfo: Ipv4-Subnet-list: 6 Name Servers, 5 different subnets (first Byte): 189., 192., 200., 201., 207., 6 different subnets (first two Bytes): 189.201., 192.100., 200.23., 200.94., 201.131., 207.248., 6 different subnets (first three Bytes): 189.201.244., 192.100.224., 200.23.1., 200.94.176., 201.131.252., 207.248.68.
AGood: Name Server IPv4-addresses from different subnet found:
AInfo: IPv6-Subnet-list: 2 Name Servers with IPv6, 1 different subnets (first block): 2001:, 2 different subnets (first two blocks): 2001:1258:, 2001:13c7:, 2 different subnets (first three blocks): 2001:1258:0000:, 2001:13c7:7000:, 2 different subnets (first four blocks): 2001:1258:0000:0000:, 2001:13c7:7000:0000:
AGood: Name Server IPv6 addresses from different subnets found.
AGood: Nameserver supports TCP connections: 8 good Nameserver
AGood: Nameserver supports Echo Capitalization: 8 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 8 good Nameserver
Nameserver doesn't pass all EDNS-Checks: m.mx-ns.mx: 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: m.mx-ns.mx: 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

Info: Creating a Letsencrypt certificate with that domain name isn't possible. To create a certificate you need a registered, worldwide unique domain name. The domain name ends with a public suffix, that's good (not Grade Z). But the domain isn't registered. If you want a certificate with that domain name, you have to proof that you are the domain owner. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
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: 56247 milliseconds, 56.247 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: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx

QNr.DomainTypeNS used
1
mx
NS
m.root-servers.net (2001:dc3::35)

Answer: c.mx-ns.mx, e.mx-ns.mx, i.mx-ns.mx, m.mx-ns.mx, o.mx-ns.mx, x.mx-ns.mx


13. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
com.mx
0

no CAA entry found
1
0
mx
0

no CAA entry found
1
0


14. TXT - Entries

No TXT entries found


15. Portchecks

No Port checks



Permalink: https://check-your-website.server-daten.de/?i=7aceade8-bbf4-47f9-b828-455ae119a7c9


Last Result: https://check-your-website.server-daten.de/?q=torneodeclubes2021powerade.com.mx - 2021-04-08 06:40:22


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

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