Whois Lookup at - shows name servers, registrar details and owner lookup for Website speed - Displays page load rate and load rates for individual elements such as JS, HTML and JPEG/GIF files for
Google Analytics - Google provides continuously updating analytics with traffic volume and user activity for
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: 2.132 220.127.116.11 2.160 You can fix this for example by adding A records to your nameservers for the zones listed above. It seems you are safe from a single point of failure. Your MX records that were reported by your nameservers are: 10 18.104.22.168 [These are all the MX records that I found.
Most users live in India - 60.0%, United States of America - 8.4%, Brazil - 3.3%, South Africa - 4.2%, Austria - 3.4%.
86.8% of users visit from a search engine, while 5.7% via a hyperlink, and 7.5% come directly - i.e.
NET Registrar URL: Name: Stephen Sandlos Registrant Organization: 1058641 Ontario Inc. In most cases, Go Daddy.com, LLC is not the registrant of domain names listed in this database.
In particular, you agree not to use this data to allow, enable, or otherwise make possible, dissemination or collection of this data, in part or in its entirety, for any purpose, such as the transmission of unsolicited advertising and and solicitations of any kind, including spam.
COM DNSSEC: unsigned For complete domain details go to: NET The data contained in Go Daddy.com, LLC's Who Is database, while believed by the company to be reliable, is provided "as is" with no guarantee or warranties regarding its accuracy.
The hosting server for was found at: Toronto, Canada.
View a map of the area and more location details for below.
Dating has totally free dating personals for singles everywhere.
Try our free dating service and find out why we have been on...
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. 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). If there are some non common MX records at your nameservers you should see them below. Looks like all your nameservers have the same set of MX records.