Domain Information for gayssex.com
-
IP-address(es)
64.156.26.75
(shared with 12 domains)
-
Nameserver(s)
ns74.webmasters.com
64.156.26.71 (29) -
Mailserver(s)
.
Keyword rankings
Search Engine Rankings
-
Google(.COM):
-
Yahoo:
Analytics / Ad-codes
- We couldn't find any analytics or ad codes on the web page
Comments
Whois record for gayssex.com
Whois
Asking
List of subdomains under gayssex.com
- www.gayssex.com A 64.156.26.75
- *.gayssex.com A 64.156.26.75
- gayssex.com A 64.156.26.75
- gayssex.com MX 0 .
- gayssex.com NS ns74.webmasters.com
- gayssex.com SOA ns74.webmasters.com
DNS report for zone gayssex.com
-
NS

- NS records from
your nameservers -
NS records got from your nameservers are:
ns11.webmasters.com [66.118.156.2]
-

- 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 gayssex.com:
ns11.webmasters.com
-

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

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

- DNS servers responded
-
Good. All nameservers listed at the parent server responded.
-

- Multiple Nameservers
-
ERR. You don't 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.
-

- Nameservers are lame
-
OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
-

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

- Different subnets
-
ERR. All your nameservers are in the 66.118.156.0/24 subnet. (C-class)
-

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

- 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

- SOA record
-
The SOA record is:
Primary nameserver: ns11.webmasters.com
Hostmaster E-mail address: admin@webmasters.com
Serial #: 952591090
Refresh: 360
Retry: 180
Expire:604800
Default TTL: 300
-

- NSs have same SOA
serial -
OK. All your nameservers agree that your SOA serial number is 952591090
-

- SOA MNAME entry
-
OK. ns11.webmasters.com That server is listed at the parent servers.
-

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

- SOA REFRESH
-
WARN Your SOA REFRESH interval is: 360. We recommend that you raise it to be within the 1200 to 43200 range. (20 minutes to 12 hours)
-

- SOA RETRY
-
OK. Your SOA RETRY value is: 600. Looks ok.
-

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

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

- MX Records
-
Your MX records that were reported by your nameservers are:
0
-

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

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

- WWW Record
-
Your www.gayssex.com record is:
www.gayssex.com [66.118.156.5]
-

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

- WWW CNAME
-
OK. No CNAME

