DNS audit for glabente.es created on 2026-08-05 13:22:06

1. Name servers

Name servers listed at the parent server h.nic.es:

ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

Result: 3 name servers found at the parent server (set at the domain provider).
Recommendation: Everything is okay. There is more than one name server added to glabente.es.

2. NS records

NS records returned by each name server configured for the domain name

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns2.inwx.es [176.97.158.104] (12ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns3.inwx.eu [45.87.158.53] (1649ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns.inwx.es [192.174.68.104] (4ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns2.inwx.es [176.97.158.104] (1ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns3.inwx.eu [45.87.158.53] (268ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns.inwx.es [192.174.68.104] (11ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns2.inwx.es [176.97.158.104] (4ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns3.inwx.eu [45.87.158.53] (168ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns.inwx.es [192.174.68.104] (0ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns2.inwx.es [176.97.158.104] (1ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns3.inwx.eu [45.87.158.53] (163ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

ns.inwx.es [192.174.68.104] (1ms):
ns2.inwx.es
ns3.inwx.eu
ns.inwx.es

Result: The NS records returned by the DNS servers are the same as the name servers set at the parent server.
Recommendation: It is not required to do any changes. All name servers are synchronized.

3. SOA record

SOA record returned by each name server configured for the domain name

San Francisco, US

ns2.inwx.es [176.97.158.104] (10ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

ns3.inwx.eu [45.87.158.53] (1647ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

ns.inwx.es [192.174.68.104] (1ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

Sydney, AU

ns2.inwx.es [176.97.158.104] (1ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

ns3.inwx.eu [45.87.158.53] (256ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

ns.inwx.es [192.174.68.104] (11ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

Johannesburg, ZA

ns2.inwx.es [176.97.158.104] (4ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

ns3.inwx.eu [45.87.158.53] (168ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

ns.inwx.es [192.174.68.104] (4ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

Singapore

ns2.inwx.es [176.97.158.104] (2ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

ns3.inwx.eu [45.87.158.53] (168ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

ns.inwx.es [192.174.68.104] (0ms):
ns.inwx.es. hostmaster.inwx.de. 2025053102 10800 3600 1209600 3600

Result: The SOA record returned by the name servers is the same on all of them.
Recommendation: It is not required to do any changes. The name servers are synchronized.

4. A record distribution by location for glabente.es

Shows how the name servers respond to requests for glabente.es

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns2.inwx.es [176.97.158.104] (12ms):
79.112.21.210

ns3.inwx.eu [45.87.158.53] (1637ms):
79.112.21.210

ns.inwx.es [192.174.68.104] (3ms):
79.112.21.210

ns2.inwx.es [176.97.158.104] (0ms):
79.112.21.210

ns3.inwx.eu [45.87.158.53] (256ms):
79.112.21.210

ns.inwx.es [192.174.68.104] (11ms):
79.112.21.210

ns2.inwx.es [176.97.158.104] (4ms):
79.112.21.210

ns3.inwx.eu [45.87.158.53] (168ms):
79.112.21.210

ns.inwx.es [192.174.68.104] (0ms):
79.112.21.210

ns2.inwx.es [176.97.158.104] (1ms):
79.112.21.210

ns3.inwx.eu [45.87.158.53] (164ms):
79.112.21.210

ns.inwx.es [192.174.68.104] (0ms):
79.112.21.210

5. A record distribution by location for www.glabente.es

Shows how the name servers respond to requests for www.glabente.es

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns2.inwx.es [176.97.158.104] (11ms):
79.112.21.210

ns3.inwx.eu [45.87.158.53] (1649ms):
79.112.21.210

ns.inwx.es [192.174.68.104] (5ms):
79.112.21.210

ns2.inwx.es [176.97.158.104] (1ms):
79.112.21.210

ns3.inwx.eu [45.87.158.53] (255ms):
79.112.21.210

ns.inwx.es [192.174.68.104] (11ms):
79.112.21.210

ns2.inwx.es [176.97.158.104] (4ms):
79.112.21.210

ns3.inwx.eu [45.87.158.53] (172ms):
79.112.21.210

ns.inwx.es [192.174.68.104] (4ms):
79.112.21.210

ns2.inwx.es [176.97.158.104] (3ms):
79.112.21.210

ns3.inwx.eu [45.87.158.53] (171ms):
79.112.21.210

ns.inwx.es [192.174.68.104] (1ms):
79.112.21.210

6. Speed

Result: During the checks in the previous steps, multiple DNS requests were executed to the name servers responsible for the domain name. Average response time of the name servers is 188.88ms.
Recommendation: The name servers respond slow. Try moving to an Anycast DNS service in order to speed up the resolution of the domain name and first page load of the web site.


Blog | Cloud DNS
Sponsored by ClouDNS