| Parent | | Domain NS records | The nameserver records obtained from the parent servers are presented here:
lady.ns.cloudflare.com. [&39;108.162.192.127&39;, &39;173.245.58.127&39;, &39;172.64.32.127&39;] (NO GLUE) [TTL=86400]
sid.ns.cloudflare.com. [&39;172.64.33.143&39;, &39;108.162.193.143&39;, &39;173.245.59.143&39;] (NO GLUE) [TTL=86400]
The server a.dns.ripn.net, in its helpfulness, directed me to sid.ns.cloudflare.com, from which this information was acquired.
A note of caution: if your domain is a country code second-level domain (ccSLD), an additional NS lookup might be necessitated, potentially causing a slight delay for your website's visitors!
|
| TLD Parent Check | This is satisfactory. The parent server I consulted, a.dns.ripn.net, possesses information pertinent to your TLD. This is advantageous, as certain other domain extensions, such as "co.us," for instance, lack direct verification capabilities. |
| Your nameservers are listed | Excellent. Your nameservers are indeed cataloged by the parent server, a.dns.ripn.net. This registration is crucial for discoverability, given that any entity unaware of your DNS servers will invariably initiate inquiries with the parent nameservers first. |
| DNS Parent sent Glue | The parent nameserver, a.dns.ripn.net, is not transmitting GLUE for all the listed nameservers. This means it is providing your nameservers' hostnames but omitting their corresponding A records. While this is acceptable, it's important to recognize that this circumstance mandates an additional A lookup, which could slightly prolong the connection times to your site. This scenario frequently arises when your nameservers reside on distinct TLDs (e.g., domain.com with nameserver ns.domain.org). |
| Nameservers A records | This is good news. Each listed nameserver possesses associated A records. This is a prerequisite for ensuring your site can be located. |
| NS | | NS records from your nameservers | The NS records retrieved from the nameservers you have designated are as follows:
lady.ns.cloudflare.com [&39;108.162.192.127&39;, &39;173.245.58.127&39;, &39;172.64.32.127&39;] [TTL=86400]
sid.ns.cloudflare.com [&39;172.64.33.143&39;, &39;108.162.193.143&39;, &39;173.245.59.143&39;] [TTL=86400]
|
| Recursive Queries | This is positive. The nameservers you are utilizing, as reported by the parent server, do not indicate that they permit recursive queries from any source. |
| Same Glue | The A records, commonly referred to as GLUE, obtained from the parent zone verification are consistent with those retrieved from your own nameservers. It is imperative that your parent server maintains identical NS records for your zone as those you have configured, in accordance with RFC guidelines. This specific check focuses solely on nameservers that are present in both the parent and your own nameserver configurations. Any absent or concealed nameservers should be visible in the subsequent listing! |
| Glue for NS records | INFORMATION: GLUE was not furnished when I requested your NS records from your nameservers. This situation is not problematic, but it is important to be aware that in such instances, an additional A record lookup becomes necessary to ascertain the IP addresses of your NS records. The nameservers that lack glue are identified as:
172.64.32.127
173.245.59.143
To rectify this, you could, for example, append A records to your nameservers for the aforementioned zones. |
| Mismatched NS records | This is acceptable. The NS records across all your designated nameservers are consistent. |
| DNS servers responded | This is good. All nameservers that are registered with the parent server have successfully responded. |
| Name of nameservers are valid | This is acceptable. All the NS records reported by your nameservers appear to be valid. |
| Multiple Nameservers | This is commendable. You have a multiplicity of nameservers. As stipulated by RFC2182 section 5, a minimum of three nameservers is required, with a maximum of seven. Having two nameservers is also acceptable. |
| Nameservers are lame | This is acceptable. Every nameserver listed by the parent servers provides authoritative responses for your domain. |
| Missing nameservers reported by parent | This is acceptable. The NS records at the parent level and those managed by your nameservers are identical. |
| Missing nameservers reported by your nameservers | This is acceptable. All the nameservers returned by the parent server, a.dns.ripn.net, are the same ones that your nameservers report. |
| Domain CNAMEs | This is acceptable. Both RFC1912 2.4 and RFC2181 10.3 stipulate that CNAME records should not coexist with NS records (or other record types). |
| NSs CNAME check | This is acceptable. As outlined in RFC1912 2.4 and RFC2181 10.3, CNAME records should not be present when NS records, or any other record type, are in existence. |
| Different subnets | This is excellent. It appears your nameservers are distributed across different subnets, which is a positive configuration! |
| IPs of nameservers are public | This is satisfactory. It appears that the IP addresses assigned to your nameservers are publicly accessible. This is beneficial as it helps to circumvent potential DNS delays and various other complications. |
| DNS servers allow TCP connection | This is acceptable. It seems that all your DNS servers permit TCP connections. This capability is advantageous and proves useful even when UDP connections are the default method of communication. |
| Different autonomous systems | This is excellent. It suggests you are protected against a single point of failure. It is crucial to remain vigilant regarding this aspect and strive to host your nameservers in diverse geographical locations, as this can mitigate numerous issues should a nameserver become unavailable. |
| Stealth NS records sent | This is acceptable. No hidden or stealth NS records have been transmitted. |
| SOA | | SOA record | The Service Authority (SOA) record is configured as follows:
Primary nameserver: lady.ns.cloudflare.com
dns.cloudflare.com
Serial : 2378632261
Refresh: 10000
Retry: 2400
Expire: 604800 1 weeks
Default TTL: 1800
|
| NSs have same SOA serial | This is acceptable. All of your nameservers are in agreement regarding your SOA serial number, which is 2378632261. |
| SOA MNAME entry | This is acceptable. The primary nameserver listed, lady.ns.cloudflare.com, is correctly registered with the parent servers. |
| SOA Serial | Your designated SOA serial number is: 2378632261. This configuration is acceptable if it aligns with your intentions and understanding. |
| SOA REFRESH | This is satisfactory. Your SOA REFRESH interval is set to: 10000, which is considered acceptable. |
| SOA RETRY | The SOA RETRY value you have set is: 2400. This appears to be within acceptable parameters. |
| SOA EXPIRE | Your SOA EXPIRE number is: 604800. This value seems to be acceptable. |
| SOA MINIMUM TTL | The SOA MINIMUM TTL, which dictates the default Time To Live for records lacking a specific TTL and now governs negative caching (indicating how long a resolver may cache a negative response), is set at: 1800. This value is considered acceptable, as RFC2308 suggests a range of 1-3 hours. Your setting of 1800 is therefore deemed appropriate. |
| MX | | MX Records | The Mail Exchanger (MX) records as reported by your nameservers are presented below:
10 mail.gaytorrent.ru 77.247.179.54
[This constitutes the entirety of the MX records identified. Should any uncommon MX records be present on your nameservers, they will be detailed in the subsequent section.] |
| Different MX records at nameservers | This is positive. It appears that all of your nameservers share an identical set of MX records. This verification process aims to identify any MX records not reported by all your nameservers, as well as MX records that share a hostname but possess different IP addresses. |
| MX name validity | This is good. No invalid hostnames were detected for your MX records. |
| MX IPs are public | This is satisfactory. All the IP addresses associated with your MX records seem to be publicly accessible. |
| MX CNAME Check | This is acceptable. No issues were detected in this regard. |
| MX A request returns CNAME | This is acceptable. No CNAME records were returned during the A record lookups. |
| MX is not IP | This is acceptable. All of your MX records are designated as hostnames. |
| Number of MX records | This is acceptable. It seems you have configured only a single MX record on your nameservers. It is advisable to proceed with caution, as this configuration presents a single point of failure, potentially leading to mail delivery disruptions if the server experiences extended downtime. |
| Mismatched MX A | This is acceptable. No discrepancies in IP addresses were found for your MX records. |
| Duplicate MX A records | This is satisfactory. Duplicate IP addresses for your MX records have not been identified, which is a favorable outcome. |
| Reverse MX A records (PTR) | Your reverse mapping (PTR) record is as follows:
54.179.247.77.in-addr.arpa -> mail.gaytorrent.ru
It is positive that you have implemented reverse (PTR) records for all your IP addresses. |
| WWW | | WWW A Record | The A record for www.gaytorrent.ru is configured as follows:
www.gaytorrent.ru [104.26.4.132] [104.26.5.132] [172.67.69.3] |
| IPs are public | This is satisfactory. All the IP addresses designated for your WWW records appear to be public IP addresses. |
| WWW CNAME | This is acceptable. No CNAME record is present. |