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

Whois

This is a cached entry from 2013-08-19 15:01:31, press here to do a realtime lookup!

Asking whois.internic.net

Asking whois.godaddy.com

List of subdomains under 80gay.com

DNS report for zone 80gay.com

Hostmaster for zone 80gay.com is: logs@dwhs.net
This is a cached entry from 2013-01-26 22:02:54, press here to do a realtime lookup!

  • Category Status Test Name Information
  • NS
    • 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 80gay.com:
      ns3.dwhs.net

    • 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.dwhs.net

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

    • check
    • DNS servers responded
    • The following of your nameservers are down:

      ns2.dwhs.net

    • 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.dwhs.net
      Hostmaster E-mail address: logs@dwhs.net
      Serial #: 2012013001
      Refresh: 86400
      Retry: 7200
      Expire:3600000
      Default TTL: 86400

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

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

    • info
    • SOA Serial
    • Your SOA serial number is: 2012013001. 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: 86400. 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:


      0 80gay.com

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

  • WWW
    • info
    • IPs are public
    • OK. All of your WWW IPs appear to be public IPs.

    • check
    • WWW CNAME
    • OK. No CNAME


bottom curve