Domain Information for indosex.info
- Keyword Position Monthly searches
Search Engine Rankings
- Search Sites Backlinks Indexed pages
Analytics / Ad-codes
- Service Code
- We couldn't find any analytics or ad codes on the web page
Whois record for indosex.info
WhoisThis is a cached entry from 2016-07-29 08:01:27, press here to do a realtime lookup!
Domain Name: INDOSEX.INFO
Domain ID: D55849581-LRMS
Referral URL: http://www.networksolutions.com/
Updated Date: 2015-11-06T20:30:47Z
Creation Date: 2015-09-07T10:06:43Z
Registry Expiry Date: 2016-09-07T10:06:43Z
Sponsoring Registrar: Domainhysteria.com LLC
Sponsoring Registrar IANA ID: 1179
Domain Status: ok https://icann.org/epp#ok
Registrant ID: md98rbc0fub7196m
Registrant Name: li hongbo
Registrant Organization: lihongbo
Registrant Street: shangdi haidian
Registrant Street: beijing
Registrant City: beijing
Registrant State/Province: Click Here to Choose
Registrant Postal Code: 100080
Registrant Country: CN
Registrant Phone: +86.13699160795
Registrant Phone Ext:
Registrant Fax Ext:
Registrant Email: email@example.com
Admin ID: j0u6d7evdg5voft7
Admin Name: li hongbo
Admin Organization: lihongbo
Admin Street: shangdi haidian
Admin Street: beijing
Admin City: beijing
Admin State/Province: Click Here to Choose
Admin Postal Code: 100080
Admin Country: CN
Admin Phone: +86.13699160795
Admin Phone Ext:
Admin Fax Ext:
Admin Email: firstname.lastname@example.org
Tech ID: j0u6d7evdg5voft7
Tech Name: li hongbo
Tech Organization: lihongbo
Tech Street: shangdi haidian
Tech Street: beijing
Tech City: beijing
Tech State/Province: Click Here to Choose
Tech Postal Code: 100080
Tech Country: CN
Tech Phone: +86.13699160795
Tech Phone Ext:
Tech Fax Ext:
Tech Email: email@example.com
Billing ID: j0u6d7evdg5voft7
Billing Name: li hongbo
Billing Organization: lihongbo
Billing Street: shangdi haidian
Billing Street: beijing
Billing City: beijing
Billing State/Province: Click Here to Choose
Billing Postal Code: 100080
Billing Country: CN
Billing Phone: +86.13699160795
Billing Phone Ext:
Billing Fax Ext:
Billing Email: firstname.lastname@example.org
Name Server: NS1.BODIS.COM
Name Server: NS2.BODIS.COM
>>> Last update of WHOIS database: 2016-07-25T12:43:52Z <<<
For more information on Whois status codes, please visit https://icann.org/epp
Access to AFILIAS WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Afilias registry database. The data in this record is provided by Afilias Limited for informational purposes only, and Afilias does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to(a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Afilias reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
List of subdomains under indosex.info
- Category Status Test Name Information
- Zone transfers
All of your nameservers disallows zone transfers (AXFR). This is good.
- 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
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.
- 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 18.104.22.168/24 subnet. (C-class)
- IPs of nameservers
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
OK. Seems all your DNS servers allow TCP connections. This is a good thing and useful even if UDP connections are used by default.
- NSs have same SOA
OK. All your nameservers agree that your SOA serial number is 2012091799
- SOA MNAME entry
OK. ns5.pacifichost.com That server is listed at the parent servers.
- SOA Serial
Your SOA serial number is: 2012091799. 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: 86400. We recommend that you lower 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: 3600000. We recommend that you lower it to be within the 1209600 to 2419200 range. (2 to 4 weeks)
- 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 Records
Your MX records that were reported by your nameservers are:
- 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.
- IPs are public
OK. All of your WWW IPs appear to be public IPs.
- WWW CNAME
OK. No CNAME