NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar. Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability. VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

NOTICE AND TERMS OF USE: The data in WEBMASTERS.COM's WHOIS database is provided for
information purposes only, and its accuracy is not guaranteed. By submitting a WHOIS
query, you agree to abide by the following terms of use: You agree that you may use this
Data only for lawful purposes and that under no circumstances will you use this Data to:
(1) allow, enable, or otherwise support the transmission of mass unsolicited, commercial
advertising or solicitations via e-mail, telephone, or fax; or (2) enable high volume,
automated, electronic processes for the purpose of re-transmitting the WHOIS data.

*** The registrant below has elected to keep their contact information private. ***

Record created on 15-Oct-1997
Record expires on 14-Oct-2013
Record updated on 12-Dec-2012 15:03:40 EST
Database last updated on 26-Jun-2013 12:34:51 EST

Domain servers in listed order:

NS73.WEBMASTERS.COM 66.230.196.127
NS74.WEBMASTERS.COM 64.156.26.71

To prevent fraudulent transfers, the above domain name has been LOCKED at the registry
level. Any request to transfer this domain name to a different owner or registrar will
require a signed, notarized authorization letter which will be verified by telephone
with the current registrant prior to approval.

-----------------------------------------------------------------------------
Get a free domain name with hosting at WEBMASTERS.COM for only $9.95 a month!
-----------------------------------------------------------------------------

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.