Domain Information for ytobe.pl
- 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 ytobe.pl
WhoisThis is a cached entry from 2014-08-20 04:24:14, press here to do a realtime lookup!
DOMAIN NAME: ytobe.pl
registrant type: organization
created: 2014.06.29 15:09:17
last modified: 2014.06.29 15:09:17
renewal date: 2015.06.29 15:09:17
company: Dom Force
street: Suite 508, Marina Towers, Newtown Barracks Road
city: NA Belize City
last modified: 2014.02.28
WHOIS displays data with a delay not exceeding 15 minutes in relation to the .pl Registry system
Registrant data available at http://dns.pl/cgi-bin/en_whois.pl
List of subdomains under ytobe.pl
- DNS Record Type Target
- *.ytobe.pl A 18.104.22.168
- *.ytobe.pl NS ns1.parkingcrew.net
- *.ytobe.pl NS ns2.parkingcrew.net
- *.ytobe.pl SOA ns1.parkingcrew.net
- ytobe.pl A 22.214.171.124
- ytobe.pl NS ns1.parkingcrew.net
- ytobe.pl NS ns2.parkingcrew.net
- ytobe.pl SOA ns1.parkingcrew.net
- www.ytobe.pl A 126.96.36.199
- www.ytobe.pl NS ns1.parkingcrew.net
- www.ytobe.pl NS ns2.parkingcrew.net
- www.ytobe.pl SOA ns1.parkingcrew.net
- 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
OK. Looks like you have nameservers on different subnets!
- 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 2012070901
- SOA MNAME entry
OK. ns2.kei.pl That server is listed at the parent servers.
- SOA Serial
Your SOA serial number is: 2012070901. Your SOA serial can pretty much be whatever you want, but most people prefer to have it in YYYYMMDD00-99 format.
- SOA REFRESH
OK. Your SOA REFRESH interval is: 10800. That is OK
- 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: 21600. 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