Domain Information for indosex.asia


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 indosex.asia

Whois

This is a cached entry from 2014-02-17 18:19:54, press here to do a realtime lookup!

Asking whois.nic.asia

List of subdomains under indosex.asia

DNS report for zone indosex.asia

Hostmaster for zone indosex.asia is:
This is a cached entry from 2013-02-15 22:24:23, 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.xtgem.com [188.95.50.129]
      ns1.xtgem.com [188.95.50.213]

    • 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
    • ERR. All your nameservers are in the 188.95.50.0/24 subnet. (C-class)

    • 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:
      Hostmaster E-mail address:
      Serial #:
      Refresh:
      Retry:
      Expire:
      Default TTL:

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

    • check
    • SOA MNAME entry
    • WARN. is not listed in the zone as a nameserver. This could mean that you're leaking information about a hidden master.

    • info
    • SOA Serial
    • Your SOA serial number is: . 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: . We recommend that you raise it to be within the 1200 to 43200 range. (20 minutes to 12 hours)

    • check
    • SOA RETRY
    • WARN. Your SOA RETRY interval is: . We recommend that you raise it to be within the 120 to 7200 range. (2 minutes to 2 hours)

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

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


bottom curve