Domain Information for itwtravelcenter.com


Keyword rankings

  • Keyword Position Monthly searches

Search Engine Rankings

  • Search Sites Backlinks Indexed pages
  • Google(.COM): loader loader
  • Yahoo: loader loader

Analytics / Ad-codes

  • Service Code
  • We couldn't find any analytics or ad codes on the web page

Comments

Whois record for itwtravelcenter.com

Whois

This is a cached entry from 2013-10-28 13:59:27, press here to do a realtime lookup!

Asking whois.internic.net

Asking whois.melbourneit.com

List of subdomains under itwtravelcenter.com

DNS report for zone itwtravelcenter.com

Hostmaster for zone itwtravelcenter.com is: hostmaster@itwhosting.com
This is a cached entry from 2013-01-26 21:42:46, press here to do a realtime lookup!

  • Category Status Test Name Information
  • NS
    • info
    • Zone transfers
    • All of your nameservers disallows zone transfers (AXFR). This is good.

    • info
    • Recursive Queries
    • I could use the nameservers listed below to performe recursive queries. It may be that I am wrong but the chances of that are low. You should not have nameservers that allow recursive queries as this will allow almost anyone to use your nameservers and can cause problems. Problem record(s) are:
      ns3.itwhosting.com
      ns2.itwhosting.net
      ns1.itwhosting.net
      ns3.itwhosting.net
      ns2.itwhosting.com
      ns1.itwhosting.com

    • check
    • Mismatched NS records
    • OK. The NS records at all your nameservers are identical.

    • check
    • DNS servers responded
    • Good. All nameservers listed at the parent server responded.

    • check
    • Multiple Nameservers
    • OK. You have multiple nameservers. In most cases 2 are enough, however, RFC2182 section 5 states that you must have at least 3 nameservers, and no more than 7.

    • check
    • Nameservers are lame
    • OK. All the nameservers listed at the parent servers answer authoritatively for your domain.

    • check
    • Domain CNAMES
    • OK. RFC1912 2.4 and RFC2181 10.3 state that there should be no CNAMEs if an NS (or any other)
      record is present.

    • check
    • Different subnets
    • OK. Looks like you have nameservers on different subnets!

    • check
    • IPs of nameservers
      are public
    • Ok. Looks like the IP addresses of your nameservers are public. This is a good thing because it will prevent DNS delays and other problems like

    • check
    • DNS servers allow
      TCP connection
    • OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.

  • SOA
    • info
    • SOA record
    • The SOA record is:
      Primary nameserver: ns1.itwhosting.com
      Hostmaster E-mail address: hostmaster@itwhosting.com
      Serial #: 16
      Refresh: 900
      Retry: 600
      Expire:86400
      Default TTL: 3600

    • info
    • NSs have same SOA
      serial
    • OK. All your nameservers agree that your SOA serial number is 16

    • check
    • SOA MNAME entry
    • OK. ns1.itwhosting.com That server is listed at the parent servers.

    • info
    • SOA Serial
    • Your SOA serial number is: 16. Your SOA serial can pretty much be whatever you want, but most people prefer to have it in YYYYMMDD00-99 format.

    • check
    • SOA REFRESH
    • WARN Your SOA REFRESH interval is: 900. We recommend that you raise it to be within the 1200 to 43200 range. (20 minutes to 12 hours)

    • check
    • SOA RETRY
    • OK. Your SOA RETRY value is: 600. Looks ok.

    • check
    • SOA EXPIRE
    • WARN. Your SOA EXPIRE interval is: 86400. We recommend that you raise it to be within the 1209600 to 2419200 range. (2 to 4 weeks)

    • check
    • SOA MINIMUM
    • OK. Your SOA MINIMUM value is: 3600. Looks ok.


bottom curve