% This is the Ukrainian Whois query server #F.
 % Rights restricted by copyright.
 %


 % % .UA whois
 % Domain Record:
 % =============
 domain: ex.ua
 admin-c: DL379-UANIC
tech-c: IMENA-UANIC
 status: BLOCKED 20120702165051
 dom-public: NO
 license: 109011
 nserver: ns1.imena.com.ua
 nserver: ns3.imena.com.ua
 nserver: ns2.imena.com.ua
 mnt-by: IMENA-UANIC (ua.imena)
remark: Доменное имя зарегистрировано в интересах клиента
 remark: The domain name has been registered on behalf of a client
 created: 0-UANIC 20090702165051
 changed: IMENA-UANIC 20120201131514
 source: UANIC


 % Administrative Contact:
 % ======================
 nic-handle: DL379-UANIC
 organization: DELIVCA LIMITED
 address: of Craigmuir Chambers, P.O. B+357ox 71
 address: 111 Tortola ROAD TOWN
 address: VG
 phone: +357 22843000
 e-mail: delivka.limited@gmail.com
 org-id: N/A
 mnt-by: NONE
 changed: DL379-UANIC 20110419121339
 source: UANIC

 % Technical Contact:
 % =================
 nic-handle: IMENA-UANIC
 organization: "Internet Invest" Ltd
 address: Gaidara st., 50
 address: 01033 KYIV
 address: UA
 fax-no: +380 (44) 2010100
 phone: +380 (44) 2010102
 e-mail: hostmaster@imena.ua
 url: http://www.imena.ua
 org-id: 32493292
 mnt-by: NONE
 changed: IMENA-UANIC 20110803163549
 source: UANIC


 % % .UA whois

 % Last update of whois database: 01 Feb 2012 13:54:35 +0200 (EET)

 % Query time: 5 msec



Дополнительная информация о домене:


 ; <<>> DiG 9.3.6-P1-RedHat-9.3.6-16.P1.el5 <<>> @127.0.0.1 ex.ua -t ANY +noquestion +nostat
 ; (1 server found)
 ;; global options: printcmd
 ;; Got answer:
 ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28124
 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 3, ADDITIONAL: 6

 ;; ANSWER SECTION:
 ex.ua. 900 IN SOA ns1.imena.com.ua. hostmaster.imena.com.ua. 2012020100 14400 7200 604800 900
 ex.ua. 900 IN A 127.0.0.1
 ex.ua. 900 IN NS ns1.imena.com.ua.
 ex.ua. 900 IN NS ns2.imena.com.ua.
 ex.ua. 900 IN NS ns3.imena.com.ua.

 ;; AUTHORITY SECTION:
 ex.ua. 900 IN NS ns3.imena.com.ua.
 ex.ua. 900 IN NS ns1.imena.com.ua.
 ex.ua. 900 IN NS ns2.imena.com.ua.

 ;; ADDITIONAL SECTION:
 ns1.imena.com.ua. 818 IN A 195.39.196.43
 ns1.imena.com.ua. 818 IN AAAA 2a02:2278:70eb:199::196:43
 ns2.imena.com.ua. 818 IN A 188.40.253.34
 ns2.imena.com.ua. 818 IN AAAA 2a01:4f8:100:22a6:188:40:253:34
 ns3.imena.com.ua. 818 IN A 88.81.249.200
 ns3.imena.com.ua. 818 IN AAAA 2a01:758:fffc:6::2



SEO показатели: PR 0, тИЦ 1400

        Category	Status	Test name	Information send feedback
Parent		Domain NS records	Nameserver records returned by the parent servers are:

ns1.imena.com.ua.   ['195.39.196.43'] (NO GLUE)   [TTL=72072]
ns2.imena.com.ua.   ['188.40.253.34'] (NO GLUE)   [TTL=72072]
ns3.imena.com.ua.   ['88.81.249.200'] (NO GLUE)   [TTL=72072]

sns-pb.isc.org was kind enough to give us that information.
	TLD Parent Check	Good. sns-pb.isc.org, the parent server I interrogated, has information for your TLD. This is a good thing as there are some other domain extensions like "co.us" for example that are missing a direct check.
	Your nameservers are listed	Good. The parent server sns-pb.isc.org has your nameservers listed. This is a must if you want to be found as anyone that does not know your DNS servers will first ask the parent nameservers.
	DNS Parent sent Glue	The parent nameserver sns-pb.isc.org is not sending out GLUE for every nameservers listed, meaning he is sending out your nameservers host names without sending the A records of those nameservers. It's ok but you have to know that this will require an extra A lookup that can delay a little the connections to your site. This happens a lot if you have nameservers on different TLD (domain.com for example with nameserver ns.domain.org.)
	Nameservers A records	Good. Every nameserver listed has A records. This is a must if you want to be found.
NS		NS records from your nameservers	NS records got from your nameservers listed at the parent NS are:

 ns2.imena.com.ua  ['188.40.253.34']   [TTL=900]
 ns1.imena.com.ua  ['195.39.196.43']   [TTL=900]
 ns3.imena.com.ua  ['88.81.249.200']   [TTL=900]

	Recursive Queries	Good. Your nameservers (the ones reported by the parent server) do not report that they allow recursive queries for anyone.
	Same Glue	The A records (the GLUE) got from the parent zone check are the same as the ones got from your nameservers. You have to make sure your parent server has the same NS records for your zone as you do according to the RFC. This tests only nameservers that are common at the parent and at your nameservers. If there are any missing or stealth nameservers you should see them below!
	Glue for NS records	OK. When I asked your nameservers for your NS records they also returned the A records for the NS records. This is a good thing as it will spare an extra A lookup needed to find those A records.
	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.
	Name of nameservers are valid	OK. All of the NS records that your nameservers report seem valid.
	Multiple Nameservers	Good. You have multiple nameservers. According to RFC2182 section 5 you must have at least 3 nameservers, and no more than 7. Having 2 nameservers is also ok by me.
	Nameservers are lame	OK. All the nameservers listed at the parent servers answer authoritatively for your domain.
	Missing nameservers reported by parent	OK. All NS records are the same at the parent and at your nameservers.
	Missing nameservers reported by your nameservers	OK. All nameservers returned by the parent server sns-pb.isc.org are the same as the ones reported by your nameservers.
	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.
	NSs CNAME check	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 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.
	Different autonomous systems	OK. It seems you are safe from a single point of failure. You must be careful about this and try to have nameservers on different locations as it can prevent a lot of problems if one nameserver goes down.
	Stealth NS records sent 	Ok. No stealth ns records are sent
SOA		SOA record	The SOA record is:
 Primary nameserver: ns1.imena.com.ua
 Hostmaster E-mail address: hostmaster.imena.com.ua
 Serial #: 2012020100
 Refresh: 14400
 Retry: 7200
 Expire: 604800   1 weeks
 Default TTL: 900
	NSs have same SOA serial	OK. All your nameservers agree that your SOA serial number is 2012020100.
	SOA MNAME entry	OK. ns1.imena.com.ua That server is listed at the parent servers.
	SOA Serial	Your SOA serial number is: 2012020100. This appears to be in the recommended format of YYYYMMDDnn.
	SOA REFRESH	OK. Your SOA REFRESH interval is: 14400. That is OK
	SOA RETRY	Your SOA RETRY value is: 7200. Looks ok
	SOA EXPIRE	Your SOA EXPIRE number is: 604800.Looks ok
	SOA MINIMUM TTL	Your SOA MINIMUM TTL is: 900. This value was used to serve as a default TTL for records without a given TTL value and now is used for negative caching (indicates how long a resolver may cache the negative answer). RFC2308 recommends a value of 1-3 hours. Your value of 900 is OK.
MX		MX Records	Oh well, I did not detect any MX records so you probably don't have any and if you know you should have then they may be missing at your nameservers!
WWW		WWW A Record	 Your www.ex.ua A record is:
 www.ex.ua  [127.0.0.1]
	IPs are public	OK. All of your WWW IPs appear to be public IPs.
	WWW CNAME	 OK. No CNAME