DNS audit for courtis.org created on 2026-10-02 06:11:43

1. Name servers

Name servers listed at the parent server b0.org.afilias-nst.org:

ns1.netregistry.net
ns2.netregistry.net
ns3.netregistry.net

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 courtis.org.

2. NS records

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

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.netregistry.net [13.248.158.180] (4ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns2.netregistry.net [75.2.118.134] (4ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns3.netregistry.net [76.223.26.245] (4ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns1.netregistry.net [13.248.158.180] (0ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns2.netregistry.net [75.2.118.134] (0ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns3.netregistry.net [76.223.26.245] (4ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns1.netregistry.net [13.248.158.180] (32ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns2.netregistry.net [75.2.118.134] (32ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns3.netregistry.net [76.223.26.245] (20ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns1.netregistry.net [13.248.158.180] (4ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns2.netregistry.net [75.2.118.134] (4ms):
drew.ns.cloudflare.com
gigi.ns.cloudflare.com

ns3.netregistry.net [76.223.26.245] (4ms):
ns1.netregistry.net
ns2.netregistry.net
ns3.netregistry.net

Result: The NS records returned by the DNS servers are not the same as the name servers set at the parent server.
Recommendation: Check the synchronization between the DNS servers. Returned NS records must be exactly the same as these returned by the parent server.

3. SOA record

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

San Francisco, US

ns1.netregistry.net [13.248.158.180] (0ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

ns2.netregistry.net [75.2.118.134] (4ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

ns3.netregistry.net [76.223.26.245] (4ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

Sydney, AU

ns1.netregistry.net [13.248.158.180] (4ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

ns2.netregistry.net [75.2.118.134] (0ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

ns3.netregistry.net [76.223.26.245] (0ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

Johannesburg, ZA

ns1.netregistry.net [13.248.158.180] (28ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

ns2.netregistry.net [75.2.118.134] (20ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

ns3.netregistry.net [76.223.26.245] (28ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

Singapore

ns1.netregistry.net [13.248.158.180] (0ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

ns2.netregistry.net [75.2.118.134] (4ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

ns3.netregistry.net [76.223.26.245] (4ms):
ns1.netregistry.net. dmain.netregistry.net. 2026100203 86400 7200 3600000 172800

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 courtis.org

Shows how the name servers respond to requests for courtis.org

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.netregistry.net [13.248.158.180] (4ms):
202.124.241.178

ns2.netregistry.net [75.2.118.134] (4ms):
202.124.241.178

ns3.netregistry.net [76.223.26.245] (4ms):
202.124.241.178

ns1.netregistry.net [13.248.158.180] (4ms):
202.124.241.178

ns2.netregistry.net [75.2.118.134] (4ms):
202.124.241.178

ns3.netregistry.net [76.223.26.245] (0ms):
202.124.241.178

ns1.netregistry.net [13.248.158.180] (32ms):
202.124.241.178

ns2.netregistry.net [75.2.118.134] (32ms):
202.124.241.178

ns3.netregistry.net [76.223.26.245] (20ms):
202.124.241.178

ns1.netregistry.net [13.248.158.180] (0ms):
202.124.241.178

ns2.netregistry.net [75.2.118.134] (4ms):
202.124.241.178

ns3.netregistry.net [76.223.26.245] (4ms):
202.124.241.178

5. A record distribution by location for www.courtis.org

Shows how the name servers respond to requests for www.courtis.org

San Francisco, US Sydney, AU Johannesburg, ZA Singapore

ns1.netregistry.net [13.248.158.180] (4ms):
202.124.241.178

ns2.netregistry.net [75.2.118.134] (0ms):
202.124.241.178

ns3.netregistry.net [76.223.26.245] (4ms):
202.124.241.178

ns1.netregistry.net [13.248.158.180] (4ms):
202.124.241.178

ns2.netregistry.net [75.2.118.134] (0ms):
202.124.241.178

ns3.netregistry.net [76.223.26.245] (0ms):
202.124.241.178

ns1.netregistry.net [13.248.158.180] (28ms):
202.124.241.178

ns2.netregistry.net [75.2.118.134] (28ms):
202.124.241.178

ns3.netregistry.net [76.223.26.245] (28ms):
202.124.241.178

ns1.netregistry.net [13.248.158.180] (4ms):
202.124.241.178

ns2.netregistry.net [75.2.118.134] (4ms):
202.124.241.178

ns3.netregistry.net [76.223.26.245] (4ms):
202.124.241.178

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 9.00ms.
Recommendation: The name servers have good response time.


Previous reports for courtis.org: 2026-10-01 01:50:17
Blog | Cloud DNS
Sponsored by ClouDNS