DNS audit for gaygineer.pro created on 2026-10-15 16:19:18

1. Name servers

Name servers listed at the parent server a2.pro.afilias-nst.info:

ns1.reg.ru
ns2.reg.ru

Result: 2 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 gaygineer.pro.

2. NS records

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

San Francisco, US Johannesburg, ZA Singapore

ns1.reg.ru [194.58.117.17] (180ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.13] (176ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.15] (180ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.15] (184ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.17] (184ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.11] (184ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.11] (184ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.13] (188ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.18] (184ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.14] (180ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.12] (188ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.16] (192ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.14] (180ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.16] (180ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.12] (188ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.18] (192ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.11] (216ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.17] (212ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.15] (216ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.13] (216ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.15] (212ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.11] (208ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.17] (212ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.13] (212ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.12] (212ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.16] (212ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.14] (212ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.18] (212ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.16] (216ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.14] (216ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.18] (216ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.12] (220ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.15] (200ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.17] (192ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.11] (188ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.13] (204ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.15] (196ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [194.58.117.17] (204ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.11] (204ms):
ns1.reg.ru
ns2.reg.ru

ns1.reg.ru [176.99.13.13] (196ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.14] (200ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.16] (212ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.18] (196ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.12] (196ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.14] (200ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.16] (208ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [176.99.13.18] (204ms):
ns1.reg.ru
ns2.reg.ru

ns2.reg.ru [194.58.117.12] (196ms):
ns1.reg.ru
ns2.reg.ru

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

ns1.reg.ru [194.58.117.17] (184ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.13] (180ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.15] (180ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.15] (176ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.17] (184ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.11] (180ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.11] (180ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.13] (180ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.18] (192ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.14] (188ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.12] (184ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.16] (184ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.14] (180ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.16] (180ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.12] (184ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.18] (180ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

Johannesburg, ZA

ns1.reg.ru [176.99.13.17] (216ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.13] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.15] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.13] (216ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.17] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.11] (216ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.15] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.11] (216ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.18] (216ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.14] (216ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.16] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.14] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.18] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.12] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.12] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.16] (208ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

Singapore

ns1.reg.ru [194.58.117.13] (192ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.15] (208ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.17] (204ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.11] (192ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.13] (212ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.15] (196ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [176.99.13.17] (196ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns1.reg.ru [194.58.117.11] (192ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.12] (200ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.14] (208ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.16] (192ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [194.58.117.18] (192ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.12] (196ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.14] (208ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.16] (200ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

ns2.reg.ru [176.99.13.18] (208ms):
ns1.reg.ru. hostmaster.ns1.reg.ru. 1768719690 14400 3600 604800 10800

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 gaygineer.pro

Shows how the name servers respond to requests for gaygineer.pro

San Francisco, US Johannesburg, ZA Singapore

ns1.reg.ru [194.58.117.13] (180ms):
77.37.234.245

ns1.reg.ru [176.99.13.13] (184ms):
77.37.234.245

ns1.reg.ru [176.99.13.11] (184ms):
77.37.234.245

ns1.reg.ru [194.58.117.11] (188ms):
77.37.234.245

ns1.reg.ru [176.99.13.17] (184ms):
77.37.234.245

ns1.reg.ru [194.58.117.17] (184ms):
77.37.234.245

ns1.reg.ru [194.58.117.15] (180ms):
77.37.234.245

ns1.reg.ru [176.99.13.15] (180ms):
77.37.234.245

ns2.reg.ru [176.99.13.18] (188ms):
77.37.234.245

ns2.reg.ru [176.99.13.14] (192ms):
77.37.234.245

ns2.reg.ru [176.99.13.12] (180ms):
77.37.234.245

ns2.reg.ru [176.99.13.16] (180ms):
77.37.234.245

ns2.reg.ru [194.58.117.14] (192ms):
77.37.234.245

ns2.reg.ru [194.58.117.16] (184ms):
77.37.234.245

ns2.reg.ru [194.58.117.12] (180ms):
77.37.234.245

ns2.reg.ru [194.58.117.18] (180ms):
77.37.234.245

ns1.reg.ru [176.99.13.15] (212ms):
77.37.234.245

ns1.reg.ru [194.58.117.11] (216ms):
77.37.234.245

ns1.reg.ru [176.99.13.17] (212ms):
77.37.234.245

ns1.reg.ru [194.58.117.17] (212ms):
77.37.234.245

ns1.reg.ru [176.99.13.11] (216ms):
77.37.234.245

ns1.reg.ru [194.58.117.15] (212ms):
77.37.234.245

ns1.reg.ru [194.58.117.13] (216ms):
77.37.234.245

ns1.reg.ru [176.99.13.13] (212ms):
77.37.234.245

ns2.reg.ru [194.58.117.12] (212ms):
77.37.234.245

ns2.reg.ru [194.58.117.18] (212ms):
77.37.234.245

ns2.reg.ru [176.99.13.14] (212ms):
77.37.234.245

ns2.reg.ru [194.58.117.16] (216ms):
77.37.234.245

ns2.reg.ru [176.99.13.12] (212ms):
77.37.234.245

ns2.reg.ru [194.58.117.14] (216ms):
77.37.234.245

ns2.reg.ru [176.99.13.18] (212ms):
77.37.234.245

ns2.reg.ru [176.99.13.16] (212ms):
77.37.234.245

ns1.reg.ru [194.58.117.11] (196ms):
77.37.234.245

ns1.reg.ru [194.58.117.13] (204ms):
77.37.234.245

ns1.reg.ru [194.58.117.15] (196ms):
77.37.234.245

ns1.reg.ru [194.58.117.17] (192ms):
77.37.234.245

ns1.reg.ru [176.99.13.11] (192ms):
77.37.234.245

ns1.reg.ru [176.99.13.13] (204ms):
77.37.234.245

ns1.reg.ru [176.99.13.15] (196ms):
77.37.234.245

ns1.reg.ru [176.99.13.17] (196ms):
77.37.234.245

ns2.reg.ru [194.58.117.12] (192ms):
77.37.234.245

ns2.reg.ru [194.58.117.14] (196ms):
77.37.234.245

ns2.reg.ru [194.58.117.16] (212ms):
77.37.234.245

ns2.reg.ru [194.58.117.18] (200ms):
77.37.234.245

ns2.reg.ru [176.99.13.12] (208ms):
77.37.234.245

ns2.reg.ru [176.99.13.14] (204ms):
77.37.234.245

ns2.reg.ru [176.99.13.16] (204ms):
77.37.234.245

ns2.reg.ru [176.99.13.18] (196ms):
77.37.234.245

5. A record distribution by location for www.gaygineer.pro

Shows how the name servers respond to requests for www.gaygineer.pro

San Francisco, US Johannesburg, ZA Singapore

ns1.reg.ru [194.58.117.17] (184ms):

ns1.reg.ru [194.58.117.13] (184ms):

ns1.reg.ru [176.99.13.15] (188ms):

ns1.reg.ru [194.58.117.15] (184ms):

ns1.reg.ru [176.99.13.17] (180ms):

ns1.reg.ru [176.99.13.11] (180ms):

ns1.reg.ru [194.58.117.11] (188ms):

ns1.reg.ru [176.99.13.13] (184ms):

ns2.reg.ru [176.99.13.18] (188ms):

ns2.reg.ru [176.99.13.14] (192ms):

ns2.reg.ru [176.99.13.12] (180ms):

ns2.reg.ru [176.99.13.16] (192ms):

ns2.reg.ru [194.58.117.14] (184ms):

ns2.reg.ru [194.58.117.16] (192ms):

ns2.reg.ru [194.58.117.12] (180ms):

ns2.reg.ru [194.58.117.18] (180ms):

ns1.reg.ru [176.99.13.13] (216ms):

ns1.reg.ru [194.58.117.11] (216ms):

ns1.reg.ru [176.99.13.17] (216ms):

ns1.reg.ru [176.99.13.11] (216ms):

ns1.reg.ru [176.99.13.15] (208ms):

ns1.reg.ru [194.58.117.13] (216ms):

ns1.reg.ru [194.58.117.15] (212ms):

ns1.reg.ru [194.58.117.17] (208ms):

ns2.reg.ru [194.58.117.16] (212ms):

ns2.reg.ru [194.58.117.18] (208ms):

ns2.reg.ru [176.99.13.16] (216ms):

ns2.reg.ru [176.99.13.18] (208ms):

ns2.reg.ru [194.58.117.12] (216ms):

ns2.reg.ru [176.99.13.12] (208ms):

ns2.reg.ru [194.58.117.14] (216ms):

ns2.reg.ru [176.99.13.14] (212ms):

ns1.reg.ru [194.58.117.13] (192ms):

ns1.reg.ru [194.58.117.15] (204ms):

ns1.reg.ru [194.58.117.17] (192ms):

ns1.reg.ru [176.99.13.11] (208ms):

ns1.reg.ru [176.99.13.13] (212ms):

ns1.reg.ru [176.99.13.15] (196ms):

ns1.reg.ru [176.99.13.17] (196ms):

ns1.reg.ru [194.58.117.11] (212ms):

ns2.reg.ru [176.99.13.12] (196ms):

ns2.reg.ru [176.99.13.14] (200ms):

ns2.reg.ru [176.99.13.16] (200ms):

ns2.reg.ru [176.99.13.18] (196ms):

ns2.reg.ru [194.58.117.12] (196ms):

ns2.reg.ru [194.58.117.14] (200ms):

ns2.reg.ru [194.58.117.16] (196ms):

ns2.reg.ru [194.58.117.18] (196ms):

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 198.77ms.
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