Domain Information for vidzip.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 vidzip.com

Whois

This is a cached entry from 2013-08-29 10:59:53, press here to do a realtime lookup!

Asking whois.internic.net

Asking whois.directnic.com

List of subdomains under vidzip.com

DNS report for zone vidzip.com

Hostmaster for zone vidzip.com is: alpha@rockbridge.com
This is a cached entry from 2013-01-26 17:17:29, 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:


      cappa.supplies.net [130.205.150.2]
      alpha.rockbridge.com [206.65.55.8]

    • info
    • Zone transfers
    • I could use the nameservers listed below to perform zone transfers. Zone transfers enables other parties to download a full list of all names under this zone. This might lead to unwanted information disclosure.

      The following servers allowed zone transfers (AXFR) for vidzip.com:
      cappa.supplies.net

    • 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:

      alpha.rockbridge.com

  • SOA
    • info
    • SOA record
    • The SOA record is:
      Primary nameserver: vidzip.com
      Hostmaster E-mail address: alpha@rockbridge.com
      Serial #: 1000000700
      Refresh: 28800
      Retry: 14400
      Expire:21600
      Default TTL: 86400

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

    • check
    • SOA MNAME entry
    • WARN. vidzip.com 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: 1000000700. 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: 28800. That is OK

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

    • check
    • SOA EXPIRE
    • WARN. Your SOA EXPIRE interval is: 21600. 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: 21600. We recommend that you lower 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:


      10 mx.supplies.net

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

    • check
    • Multiple MX
    • WARN. You have one MX-record. You should look into getting a backup mailserver for increased redundancy.


bottom curve