| Section | Status | Lookup Test Name | DNS Query Results |
|---|---|---|---|
WWW |
 |
WWW A Record |
A Record / Server IP-Address for Domain www.viventiabiotech.net is: [ 141.8.225.31 ]
|
 |
IP Addresses are public |
All of your WWW IP Addresses appear to be public IPs. |
|
|
Hostname FQDN |
Server Hostname FQDN is: 141.8.225.31 |
|
Parent |
|
Domain NS Records |
Name Server Records returned by the parent servers are:
viventiabiotech.net. 172800 IN NS ns75.worldnic.com.
viventiabiotech.net. 172800 IN NS ns76.worldnic.com. a.gtld-servers.net was kind enough to give us that information.
|
|
TLD Parent Check |
Good. a.gtld-servers.net, the parent server I interrogated, has information for your TLD. |
|
|
Name Servers listed |
The parent server a.gtld-servers.net has your name servers listed. This is a must if you want to be found as anyone that does not know your DNS Servers will first ask the parent name servers. |
|
 |
DNS Parent send Glue |
The parent nameserver might not sent your name servers as well as the IPs of your name servers. Glue Records are A Records that are associated with NS Records to provide bootstrapping information to the nameserver. |
|
|
Nameserver A Records |
Every nameserver listed probably has A Records. This is a must if you want to be found. |
|
NS |
|
NS Records from your Name Servers |
NS Records got from your nameservers listed at the parent NS are:
|
|
Mismatched NS Records |
The NS Records at all your name servers are identical. |
|
|
Recursive NS Queries |
Nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone. |
|
|
DNS Servers responded |
All name servers listed at the parent server responded. |
|
|
Name of Nameservers are valid |
All of the NS Records that your name servers report seem valid. |
|
|
Multiple Name Servers |
It seems you don't have multiple name servers. You must have at least 3 name servers, and no more than 7. Having 2 name servers is also ok. |
|
 |
Missing name servers reported by your name servers |
DNS ERROR: One or more of the name servers listed at the parent servers are not listed as NS Records at your name servers. The problem NS Records are:
ns75.worldnic.com
ns76.worldnic.com This is listed as an DNS ERROR because there are some cases where nasty problems can occur (if the TTLs vary from the NS Records at the root servers and the NS Records point to your own domain, for example).
|
|
|
Domain CNAMEs |
RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. |
|
|
NS CNAME Checks |
RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other) record is present. |
|
|
Nameservers are lame |
All nameserver listed at the parent servers answer authoritatively for your domain. |
|
|
Missing name servers reported by parent |
All NS Records are the same at the parent and at your name servers. |
|
|
Missing Nameservers reported by your Nameservers |
All nameservers returned by the parent server f.gtld-servers.net are the same as the ones reported by your nameservers. |
|
|
IPs of Nameservers are public |
Looks like the IP addresses of your name servers are public. This is a good thing because it will prevent DNS delays and other problems. |
|
|
Same Glue |
The A Records (Same GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS Records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below! |
|
|
Glue for NS Records |
INFO: GLUE was not sent when I asked your nameservers for your NS Records.This is ok but you should know that in this case an extra A record lookup is required in order to get the IPs of your NS Records. The nameservers without glue are:
|
|
|
Different Subnets |
Looks like you have nameservers on different subnets. |
|
|
DNS Servers allow TCP connection |
Seems all your DNS Servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default. |
|
|
Different autonomous systems |
It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down. |
|
|
Stealth NS Records sent |
No stealth NS Records are sent |
|
SOA |
|
SOA Record |
The SOA record is:
Primary nameserver:
Hostmaster eMail-Address:
Serial #:
Refresh:
Retry:
Expire:
Default TTL: |
|
NSs have same SOA Serial |
All nameservers agree that your SOA Serial Number is:
|
|
|
SOA MNAME entry |
That server is not listed at the parent servers. |
|
|
SOA Serial No. |
SOA Serial Number is: . This can be ok if you know what you are doing. |
|
|
SOA REFRESH |
Looks not within recommended range. SOA REFRESH interval is: . |
|
|
SOA RETRY |
SOA RETRY value is: . Looks not within recommended range. |
|
|
SOA EXPIRE |
SOA EXPIRE number is: . That is not OK |
|
|
SOA MINIMUM TTL |
SOA MINIMUM TTL is: . This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). Recommended value is 1-3 hours. |
|
MX |
|
MX Records |
Your MX records that were reported by your name servers are:
[All these MX Records were found. If there are some non common MX records at your nameservers you should see them below.] |
|
MX Name Validity |
Good. I did not detect any invalid hostnames for your MX records. |
|
|
MX IPs are public |
All of your MX records appear to use public IPs. |
|
|
MX is not IP |
All of MX records are host names. |
|
|
Number of MX Records |
Looks like you only have one MX record at your name servers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time. |
|
|
Different MX Records at Nameservers |
Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs |
|
|
Mismatched MX A |
OK. I did not detect differing IPs for your MX records. |
|
|
Duplicate MX A Records |
OK. I have not found duplicate IPs for your MX records. This is a good thing. |
|
|
MX A request returns CNAME |
OK. No CNAMEs returned for A records lookups. |
|
|
MX CNAME Check |
DNS Query has not found any errors in MX CNAME. |
|
Ping |
|
PING viventiabiotech.net (141.8.225.31) 56(84) bytes of data. 64 bytes from 141.8.225.31: icmp_seq=1 ttl=237 time=115 ms 64 bytes from 141.8.225.31: icmp_seq=2 ttl=237 time=116 ms --- viventiabiotech.net ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 1001ms rtt min/avg/max/mdev = 115.854/116.045/116.237/0.390 ms |
