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


 

 

X

 

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

 

Checked:
31.08.2026 17:42:39

 

Older results

No older results found

 

1. IP-Addresses

HostTypeIP-Addressis auth.∑ Queries∑ Timeout
zentra.nuanet.com.mx
A
158.23.87.248
Querétaro City/Querétaro/Mexico (MX) - Microsoft Corporation
No Hostname found
yes
1
0

AAAA

yes


www.zentra.nuanet.com.mx

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



AAAA
Name Error
yes



CNAME
Name Error
yes


*.zentra.nuanet.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 20326, Flags 257 (SEP = Secure Entry Point)






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






Public Key with Algorithm 8, KeyTag 57780, Flags 256






1 RRSIG RR to validate DNSKEY RR found






RRSIG-Owner (root), Algorithm: 8, 0 Labels, original TTL: 172800 sec, Signature-expiration: 20.09.2026, 00:00:00 +, Signature-Inception: 30.08.2026, 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 43850, DigestType 2 and Digest PUSB9tyPpwiQOJG9BkgcYGnTe6okECLjaZrIkoaT2+8=






1 RRSIG RR to validate DS RR found






RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 13.09.2026, 05:00:00 +, Signature-Inception: 31.08.2026, 04:00:00 +, KeyTag 57780, Signer-Name: (root)






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 39379, Flags 256






Public Key with Algorithm 8, KeyTag 40053, Flags 256






Public Key with Algorithm 8, KeyTag 43850, 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: 30.09.2026, 00:00:00 +, Signature-Inception: 31.08.2026, 00:00:00 +, KeyTag 39379, Signer-Name: mx






RRSIG-Owner mx., Algorithm: 8, 1 Labels, original TTL: 86400 sec, Signature-expiration: 29.10.2026, 16:00:00 +, Signature-Inception: 30.08.2026, 15:00:00 +, KeyTag 43850, Signer-Name: mx






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






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






Status: Valid Chain of trust. Parent-DS with Algorithm 8, KeyTag 43850, DigestType 2 and Digest "PUSB9tyPpwiQOJG9BkgcYGnTe6okECLjaZrIkoaT2+8=" 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 43850, DigestType 2 and Digest HFPno/ZxcIXMiNIjHK+IwygUVlMLzqjcDzTroudbFL8=






1 RRSIG RR to validate DS RR found






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






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






3 DNSKEY RR found






Public Key with Algorithm 8, KeyTag 39379, Flags 256






Public Key with Algorithm 8, KeyTag 40053, Flags 256






Public Key with Algorithm 8, KeyTag 43850, 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: 30.09.2026, 00:00:00 +, Signature-Inception: 31.08.2026, 00:00:00 +, KeyTag 39379, Signer-Name: com.mx






RRSIG-Owner com.mx., Algorithm: 8, 2 Labels, original TTL: 86400 sec, Signature-expiration: 29.10.2026, 16:00:00 +, Signature-Inception: 30.08.2026, 15:00:00 +, KeyTag 43850, Signer-Name: com.mx






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






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






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



Zone: nuanet.com.mx

nuanet.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 "ag0qurokvsk7sjl4vkld377i34hihaab" between the hashed NSEC3-owner "afv8ildot0tr6mh9uvb345pkcg5u4uvb" and the hashed NextOwner "ag1sbiv94subetvd1np7i4k25p0k6jtp". So the parent zone confirmes the not-existence of a DS RR.
Bitmap: NS, DS, RRSIG Validated: RRSIG-Owner afv8ildot0tr6mh9uvb345pkcg5u4uvb.com.mx., Algorithm: 8, 3 Labels, original TTL: 1800 sec, Signature-expiration: 30.09.2026, 00:00:00 +, Signature-Inception: 31.08.2026, 00:00:00 +, KeyTag 39379, Signer-Name: com.mx






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






0 DNSKEY RR found









Zone: zentra.nuanet.com.mx

zentra.nuanet.com.mx
0 DS RR in the parent zone found






0 DNSKEY RR found









Zone: www.zentra.nuanet.com.mx

www.zentra.nuanet.com.mx
0 DS RR in the parent zone found

 

3. Name Servers

DomainNameserverNS-IP
www.zentra.nuanet.com.mx
  ns1.wix.com

zentra.nuanet.com.mx
  ns1.wix.com / Nv��p0x�ֈ���x
216.239.32.100
Mountain View/California/United States (US) - Google LLC

nuanet.com.mx
  ns1.wix.com / hex:47 CB 89 ED FF E5 10 B3 A7 C6 3B 9B 0B 31 B0 A8
216.239.32.100
Mountain View/California/United States (US) - Google LLC


  ns2.wix.com / ���=�����*�R����
216.239.32.100
Mountain View/California/United States (US) - Google LLC

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


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


  e.mx-ns.mx
189.201.244.1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México


 
2801:c4:c0::1
Monterrey/Nuevo León/Mexico (MX) - WoodyNet, Inc.


  i.mx-ns.mx
207.248.68.1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México


T 
2801:c4:d0::1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México


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


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


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


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


  x.mx-ns.mx
201.131.252.1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México


 
2001:1201:10::1
Monterrey/Nuevo León/Mexico (MX) - Network Information Center México

mx
  c.mx-ns.mx


  e.mx-ns.mx


  i.mx-ns.mx


  m.mx-ns.mx


  o.mx-ns.mx


  x.mx-ns.mx

 

4. SOA-Entries


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


Domain:nuanet.com.mx
Zone-Name:nuanet.com.mx
Primary:ns1.wix.com
Mail:support.wix.com
Serial:2025091203
Refresh:10800
Retry:3600
Expire:1209600
TTL:3600
num Entries:2


Domain:zentra.nuanet.com.mx
Zone-Name:nuanet.com.mx
Primary:ns1.wix.com
Mail:support.wix.com
Serial:2025091203
Refresh:10800
Retry:3600
Expire:1209600
TTL:3600
num Entries:1


Domain:www.zentra.nuanet.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
• http://zentra.nuanet.com.mx/
158.23.87.248
-14


10.046
T
Timeout - The operation has timed out.

• https://zentra.nuanet.com.mx/
158.23.87.248
-14


10.030
T
Timeout - The operation has timed out.

• http://zentra.nuanet.com.mx/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
158.23.87.248
-14


10.047
T
Timeout - The operation has timed out.
Visible Content:

• https://158.23.87.248/
158.23.87.248
-14


10.017
T
Timeout - The operation has timed out.

 

7. Comments


1. General Results, most used to calculate the result

Aname "zentra.nuanet.com.mx" is subdomain, 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: 444 (complete: 276475)
AGood: All ip addresses are public addresses
Warning: Only one ip address found: zentra.nuanet.com.mx has only one ip address.
Warning: No ipv6 address found. Ipv6 is the future with a lot of new features. So every domain name should have an ipv6 address. See https://en.wikipedia.org/wiki/IPv6: zentra.nuanet.com.mx has no ipv6 address.
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.
XFatal error: Nameserver doesn't support TCP connection: c.mx-ns.mx / 192.100.224.1: Fatal error (-14). Details: Unable to read data from the transport connection: Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat.. - Ein Verbindungsversuch ist fehlgeschlagen, da die Gegenstelle nach einer bestimmten Zeitspanne nicht richtig reagiert hat, oder die hergestellte Verbindung war fehlerhaft, da der verbundene Host nicht reagiert hat
XFatal error: Nameserver doesn't support TCP connection: e.mx-ns.mx / 189.201.244.1: Timeout
Info: Checking the ip addresses of that domain name not exact one certificate found. So it's impossible to check if that domain requires Server Name Indication (SNI).: Domain zentra.nuanet.com.mx, 1 ip addresses.
BNo _mta-sts TXT record found (mta-sts: Mail Transfer Agent Strict Transport Security - see RFC 8461). Read the result of server-daten.de (Url-Checks, Comments, Connections and DomainServiceRecords) to see a complete definition. Domainname: _mta-sts.zentra.nuanet.com.mx

2. Header-Checks

U

No https result with http status 2** or 4** (standard-check) found, no header checked.

3. DNS- and NameServer - Checks

AInfo:: 20 Root-climbing DNS Queries required to find all IPv4- and IPv6-Addresses of 2 Name Servers.
AInfo:: 20 Queries complete, 20 with IPv6, 0 with IPv4.
AGood: All DNS Queries done via IPv6.
Bad (greater 8):: An average of 10.0 queries per domain name server required to find all ip addresses of all name servers.
AInfo:: 2 different Name Servers found: ns1.wix.com, ns2.wix.com, 2 Name Servers included in Delegation: ns1.wix.com, ns2.wix.com, 2 Name Servers included in 1 Zone definitions: ns1.wix.com, ns2.wix.com, 1 Name Servers listed in SOA.Primary: ns1.wix.com.
AGood: Only one SOA.Primary Name Server found.: ns1.wix.com.
AGood: SOA.Primary Name Server included in the delegation set.: ns1.wix.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.wix.com, ns2.wix.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: 2 different Name Servers found
Warning: No Name Server IPv6 address found. IPv6 is the future, so your name servers should be visible via IPv6.: 2 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.: 2 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: wix.com
Warning: All Name Servers from the same Country / IP location.: 2 Name Servers, 1 Countries: US
AInfo: Ipv4-Subnet-list: 2 Name Servers, 1 different subnets (first Byte): 216., 1 different subnets (first two Bytes): 216.239., 1 different subnets (first three Bytes): 216.239.32.
XFatal: All Name Server IPv4 addresses from the same subnet. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.:
XFatal: Only one Name Server IPv4 address found. Check https://www.iana.org/help/nameserver-requirements to learn some basics about name server configurations. If you manage these name servers, fix it. If it's your provider, change your provider.
AGood: Nameserver supports TCP connections: 1 good Nameserver
AGood: Nameserver supports Echo Capitalization: 1 good Nameserver
AGood: Nameserver supports EDNS with max. 512 Byte Udp payload, message is smaller: 1 good Nameserver
XNameserver Timeout checking EDNS512: i.mx-ns.mx / 2801:c4:d0::1
AGood: Nameserver has passed 10 EDNS-Checks (OP100, FLAGS, V1, V1OP100, V1FLAGS, DNSSEC, V1DNSSEC, NSID, COOKIE, CLIENTSUBNET): 1 good Nameserver
Nameserver doesn't pass all EDNS-Checks: ns1.wix.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: o.mx-ns.mx / 2001:1201::1: OP100: ok. FLAGS: ok. V1: ok. V1OP100: ok. V1FLAGS: ok. DNSSEC: ok. V1DNSSEC: fatal timeout. NSID: ok. 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.

4. Content- and Performance-critical Checks

http://zentra.nuanet.com.mx/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 158.23.87.248
-14

Fatal: Check of /.well-known/acme-challenge/random-filename has a timeout. Creating a Letsencrypt certificate via http-01 challenge can't work. You need a running webserver (http) and an open port 80. If it's a home server + ipv4, perhaps a correct port forwarding port 80 extern ⇒ working port intern is required. Port 80 / http can redirect to another domain port 80 or port 443, but not other ports. If it's a home server, perhaps your ISP blocks port 80. Then you may use the dns-01 challenge. Trouble creating a certificate? Use https://community.letsencrypt.org/ to ask.
AInfo: No img element found, no alt attribute checked
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: 179220 milliseconds, 179.220 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" > of the last months 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. Html-Parsing via https://validator.w3.org/nu/


No https result http status 200 and Content-Type text/html or text/xml found, no Html-Parsing - Check

 

13. Nameserver - IP-Adresses

Required Root-climbing DNS-Queries to find ip addresses of all Name Servers: ns1.wix.com, ns2.wix.com

 

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

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.wix.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net
3
ns2.wix.com
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p03.nsone.net, dns2.p03.nsone.net, dns3.p03.nsone.net, dns4.p03.nsone.net
4
net
NS
d.root-servers.net (2001:500:2d::d)

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
5
dns1.p03.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
6
dns2.p03.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
7
dns3.p03.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
8
dns4.p03.nsone.net
NS
a.gtld-servers.net (2001:503:a83e::2:30)

Answer: dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net

Answer: dns1.p01.nsone.net
198.51.44.1, 2620:4d:4000:6259:7:1:0:1

Answer: dns2.p01.nsone.net
198.51.45.1, 2a00:edc0:6259:7:1::2

Answer: dns3.p01.nsone.net
198.51.44.65, 2620:4d:4000:6259:7:1:0:3

Answer: dns4.p01.nsone.net
198.51.45.65, 2a00:edc0:6259:7:1::4
9
dns1.p03.nsone.net: 198.51.44.3
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
10
dns1.p03.nsone.net: 2620:4d:4000:6259:7:3:0:1
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
11
dns2.p03.nsone.net: 198.51.45.3
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
12
dns2.p03.nsone.net: 2a00:edc0:6259:7:3::2
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
13
dns3.p03.nsone.net: 198.51.44.67
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
14
dns3.p03.nsone.net: 2620:4d:4000:6259:7:3:0:3
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
15
dns4.p03.nsone.net: 198.51.45.67
A
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
16
dns4.p03.nsone.net: 2a00:edc0:6259:7:3::4
AAAA
dns1.p01.nsone.net (2620:4d:4000:6259:7:1:0:1)
17
ns1.wix.com: 216.239.32.100
A
dns1.p03.nsone.net (2620:4d:4000:6259:7:3:0:1)
18
ns1.wix.com: No AAAA record found
AAAA
dns1.p03.nsone.net (2620:4d:4000:6259:7:3:0:1)
19
ns2.wix.com: 216.239.32.100
A
dns1.p03.nsone.net (2620:4d:4000:6259:7:3:0:1)
20
ns2.wix.com: No AAAA record found
AAAA
dns1.p03.nsone.net (2620:4d:4000:6259:7:3:0:1)

 

14. CAA - Entries

DomainnameflagNameValue∑ Queries∑ Timeout
zentra.nuanet.com.mx
0

no CAA entry found
1
0
nuanet.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

 

15. TXT - Entries

DomainnameTXT EntryStatus∑ Queries∑ Timeout
nuanet.com.mx
atlassian-domain-verification=1lNil3zA9D2zLOv4Yg5pPorKAmuRN1zLj5Sk4ZqQ63W6COLHAEed9CWc8g/Klxuj
ok
1
0
nuanet.com.mx
atlassian-sending-domain-verification=6a7076a7-411f-4be0-b04d-c88d94402f44
ok
1
0
nuanet.com.mx
cisco-ci-domain-verification=4e2729f727b158574e3db2eb2022524beacda45b6afc21109ee04314cd65c181
ok
1
0
nuanet.com.mx
duo_sso_verification=uPyc2VKBqkTVgZLr5B1bBRAssLrMpOMv0Fe3lnPHttE2jsOOOhHjZLo52NsKy3qc
ok
1
0
nuanet.com.mx
f2e4rmf0677lig45atjfpp578p
ok
1
0
nuanet.com.mx
google-site-verification=6PBXP3_3joFeHdFQgDTnJVLmOoJIlyXxi207HM6E40A
ok
1
0
nuanet.com.mx
google-site-verification=sadI7Fy6Qvz42LJiDSsqrDY-vCsbD-zVK0i4uao9Ojk
ok
1
0
nuanet.com.mx
google-site-verification=Vl8RBez48RNK5beCkv_jdIsoI_TvQLGEWRHd9QAIh4E
ok
1
0
nuanet.com.mx
v=spf1 include:spf.protection.outlook.com include:zift123.com ip4:52.49.77.121 -all
ok
1
0
zentra.nuanet.com.mx

ok
1
0
_acme-challenge.zentra.nuanet.com.mx

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

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

Name Error - The domain name does not exist
1
0

 

16. DomainService - Entries

No DomainServiceEntries entries found

 

 

17. Cipher Suites

No results

 

18. Portchecks

No open Ports <> 80 / 443 found, so no additional Ports checked.

 

 

Permalink: https://check-your-website.server-daten.de/?i=2637b838-7cba-414f-b681-e2f0d6d64bdd

 

Last Result: https://check-your-website.server-daten.de/?q=zentra.nuanet.com.mx - 2026-08-31 17:42:39

 

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

 

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

 

 

Do you really want to support this project? Donate: Check-your-website, IBAN DE98 1001 0010 0575 2211 07, SWIFT/BIC PBNKDEFF, Euro

 

QR-Code of this page - https://check-your-website.server-daten.de/?d=zentra.nuanet.com.mx