Domain Information for anthemdentaladmin.com


Keyword rankings

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 anthemdentaladmin.com

Whois

This is a cached entry from 2013-08-18 09:08:07, press here to do a realtime lookup!

Asking whois.internic.net

Asking whois.melbourneit.com

List of subdomains under anthemdentaladmin.com

DNS report for zone anthemdentaladmin.com

Hostmaster for zone anthemdentaladmin.com is: security@decare.com
This is a cached entry from 2013-01-31 04:43:04, press here to do a realtime lookup!

  • Category Status Test Name Information
  • NS
    • info
    • NS records from
      your nameservers
    • NS records got from your nameservers are:


      ns2.decare.com [65.91.174.136]
      ns1.decare.com [74.203.213.136]

    • info
    • Zone transfers
    • All of your nameservers disallows zone transfers (AXFR). This is good.

    • info
    • Recursive Queries
    • All of your nameservers disallows recursive queries. This is good.

    • 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
    • ERR. The following servers does not allow queries via TCP:

      ns2.decare.com ns1.decare.com

  • SOA
    • info
    • SOA record
    • The SOA record is:
      Primary nameserver: ns1.decare.com
      Hostmaster E-mail address: security@decare.com
      Serial #: 2010080912
      Refresh: 10800
      Retry: 3600
      Expire:2592000
      Default TTL: 28800

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

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

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

    • check
    • SOA REFRESH
    • OK. Your SOA REFRESH interval is: 10800. That is OK

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

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

    • check
    • SOA MINIMUM
    • WARN. Your SOA MINIMUM interval is: 900. We recommend that you raise it to be within the 3600 to 10800 range. (1 to 3 hours)

  • MX
    • info
    • MX Records
    • Your MX records that were reported by your nameservers are:


      20 cluster5a.us.messagelabs.com
      10 cluster5.us.messagelabs.com

    • check
    • MX is not IP
    • OK. All of your MX records are host names.

    • check
    • Multiple MX
    • OK. You have multiple mailservers. (2 MX records detected)


bottom curve