DNS Report
Просмотрите полный отчет о настройках DNS для своего домена. Этот инструмент разработан, чтобы помочь веб-мастерам и системным администраторам диагностировать связанные с DNS проблемы.
DNSreport - bokepxv.com/lolitasstar-beautiful-orgasm-porn.
| How I am searching: Searching for bokepxv.com/lolitasstar-beautiful-orgasm-porn. record at b.root-servers.net [170.247.170.2]: Reports bokepxv.com/lolitasstar-beautiful-orgasm-porn. [took 35 ms] |
| Category | Status | Test name | Information |
|---|---|---|---|
| Parent | FAILED | Parent nameservers have your nameservers listed | FAILED. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. |
| FAILED | DNS servers have A records | FAILED. Parent servers not have A records for ??? | |
| INFO | NS records at parent servers | Your NS records at the parent servers are: | |
| NS | INFO | NS records at your nameservers | Your NS records at your nameservers are: |
| WARN | No NS A records at nameservers | WARNING. Your nameservers do not include corresponding A records when asked for your NS records. This ensures that your DNS servers know the A records corresponding to all your NS records. | |
| FAILED | Open DNS servers | FAILED. Your DNS servers was announce that they are open DNS servers. Although there is a slight chance that they really are open DNS servers, this is very unlikely. Open DNS servers increase the chances that of cache poisoning, can degrade performance of your DNS, and can cause your DNS servers to be used in an attack (so it is good that your DNS servers do not appear to be open DNS servers). | |
| FAILED | All nameservers report identical NS records | FAILED. The NS records at all your nameservers are not identical. | |
| FAILED | All nameservers respond | FAILED. Not all of your nameservers listed at the parent nameservers responded: | |
| FAILED | Number of nameservers | FAILED. You have 0 nameservers. You must have at least 2 nameservers. | |
| FAILED | Missing nameservers | FAILED. Not all of the nameservers listed at the parent nameservers are also listed as NS records at your nameservers. | |
| FAILED | Missing nameservers (reversed) | FAILED. Not all 0 of your nameservers (as reported by your nameservers) are also listed at the parent servers. | |
| FAILED | No CNAMEs for domain | FAILED. There are CNAMEs for bokepxv.com/lolitasstar-beautiful-orgasm-porn. | |
| FAILED | No NSs with CNAMEs | FAILED. There are CNAMEs for your NS records. | |
| FAILED | Nameservers on separate class C | FAILED. You not have nameservers on different Class C (technically, /24) IP ranges. You must have nameservers at geographically and topologically dispersed locations. | |
| FAILED | All NS IPs public | FAILED. Not all of your NS records appear to use public IPs. If there were any private IPs, they would not be reachable, causing DNS delays. | |
| FAILED | TCP Allowed | FAILED. Not all your DNS servers allow TCP connections. Although rarely used, TCP connections are occasionally used instead of UDP connections. When firewalls block the TCP DNS connections, it can cause hard-to-diagnose problems. | |
| INFO | Nameservers versions | Your nameservers have the following versions: | |
| SOA | INFO | SOA record | Your SOA record is: |
| FAILED | NS agreement on SOA Serial | FAILED. Your nameservers have different SOA serial. | |
| FAILED | SOA MNAME Check | FAILED. Your SOA (Start of Authority) record states that your master (primary) name server is: That server is listed at the parent servers, which is not correct. | |
| FAILED | SOA RNAME Check | FAILED. Your SOA (Start of Authority) record states that your DNS contact E-mail address is: . (techie note: we have changed the initial '.' to an '@' for display purposes). | |
| FAILED | SOA Serial Number | FAILED. Your SOA serial number is: . This appears to be in the recommended format of YYYYMMDDnn, where 'nn' is the revision. So this indicates that your DNS was last updated on 30 Nov 1999. | |
| WARN | SOA REFRESH value | WARNING. Your SOA REFRESH interval is: seconds. The normal interval is about 1200-43200 seconds (20 minutes to 12 hours). This value determines how often secondary/slave nameservers check with the master for updates. | |
| WARN | SOA RETRY value | WARNING. Your SOA RETRY interval is: seconds. The normal interval is about 120-7200 seconds. The retry value is the amount of time your secondary/slave nameservers will wait to contact the master nameserver again if the last attempt failed. | |
| WARN | SOA EXPIRE value | WARNING. Your SOA EXPIRE time: seconds. The normal interval is about 1209600-2419200 seconds (2-4 weeks). This is how long a secondary/slave nameserver will wait before considering its DNS data stale if it can't reach the primary nameserver. | |
| WARN | SOA MINIMUM TTL value | WARNING. Your SOA MINIMUM TTL is: seconds. The normal interval is about 3600-10800 seconds (1-3 hours). This value used to determine the default (technically, minimum) TTL (time-to-live) for DNS entries, but now is used for negative caching. | |
| MX | INFO | MX Record | Your 0 MX records are: |
| FAILED | Invalid characters | FAILED. Not all of your MX records appear to use valid hostnames, without any invalid characters. | |
| FAILED | All MX IPs public | FAILED. Not all of your MX records appear to use public IPs. If there were any private IPs, they would not be reachable, causing slight mail delays, extra resource usage, and possibly bounced mail. | |
| FAILED | MX records are not CNAMEs | FAILED. Looking up your MX record was just return a CNAME. If an MX record query returns a CNAME, extra processing is required, and some mail servers may not be able to handle it. | |
| FAILED | MX is host name, not IP | FAILED. Not all of your MX records are host names (as opposed to IP addresses, which are not allowed in MX records). | |
| FAILED | Multiple MX records | FAILED. You do not have multiple MX records. This means that if one is down or unreachable, the other(s) will be able to accept mail for you. | |
| FAILED | Differing MX-A records | FAILED. I was detect differing IPs for your MX records: This would happen if your DNS servers return different IPs than the DNS servers that are authoritative for the hostname in your MX records. | |
| FAILED | Duplicate MX records | FAILED. 0 duplicate MX records (pointing to the same IP). Although technically valid, duplicate MX records can cause a lot of confusion, and waste resources. | |
| FAILED | Reverse DNS entries for MX records | FAILED. The IPs of not all of your mail server(s) have correct reverse DNS (PTR) entries. The reverse DNS entries are: | |
| FAILED | Connect to mail servers | FAILED. You were not able to connect to: | |
| FAILED | Mail server host name in greeting | FAILED. Not all of your mailservers have their host name in the greeting: | |
| INFO | Sending test mail | Unable to connect to host | |
| PASS | Open relay test | OK. All of your mailservers appear to be closed to relaying. | |
| FAILED | SPF record | FAILED. You don't seem to have an SPF record. This is not very good, as the SPF record helps to prevent spammers from abusing your domain. | |
| WWW | INFO | WWW Record | Your www.bokepxv.com/lolitasstar-beautiful-orgasm-porn. A record is: |
| FAILED | All WWW IPs public | FAILED. Not all of your WWW IPs appear to be public IPs. If there were any private IPs, they would not be reachable, causing problems reaching your web site. | |
| FAILED | CNAME Lookup | FAILED. Your web site (www.bokepxv.com/lolitasstar-beautiful-orgasm-porn.) has a CNAME record. | |
| INFO | Domain A Lookup | Your bokepxv.com/lolitasstar-beautiful-orgasm-porn. A record is: | |
| FAILED | Connect to HTTP servers | FAILED. You were not able to connect to your HTTP server. |