Domain Information for belatin.com

  • Category Information
  • IP-address(es)
  • Nameserver(s)
  • Mailserver(s)

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

Whois

This is a cached entry from 2013-09-08 11:21:53, press here to do a realtime lookup!

Asking whois.internic.net

Asking whois.netregistry.net

List of subdomains under belatin.com

  • DNS Record Type Target
  •     belatin.com has no DNS records

DNS report for zone belatin.com

Hostmaster for zone belatin.com is: dmain@netregistry.net
This is a cached entry from 2013-02-05 01:18:24, 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
    • 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
    • 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.netregistry.net
      Hostmaster E-mail address: dmain@netregistry.net
      Serial #: 2012110508
      Refresh: 86400
      Retry: 7200
      Expire:3600000
      Default TTL: 3600

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

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

    • info
    • SOA Serial
    • Your SOA serial number is: 2012110508. 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: 86400. We recommend that you lower 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: 3600000. 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: 172800. We recommend that you lower it to be within the 3600 to 10800 range. (1 to 3 hours)


bottom curve