citysearch3.com


DNS delegation of citysearch3.com updated: May 24, 2013 1:08:57 PM

Delegation

stepqueryauthservers
1citysearch3.com..(k,c,b,g,e,h,a,d,j,f,m,i,l).root-servers.net.
2citysearch3.com.com.(m,e,f,g,k,j,h,b,d,a,i,l,c).gtld-servers.net.
3citysearch3.com.citysearch3.com.(ns2,ns3,ns1).citygrid.com.
4redir2.citysearch.com.com.(h,d,g,a,c,k,f,j,m,b,i,e,l).gtld-servers.net.
5redir2.citysearch.com.citysearch.com.(ns2,ns3,ns1).citygrid.com.
6cspxy-vip.citysearch.com.citysearch.com.(ns3,ns1,ns2).citygrid.com.
7cspxy-vip.aws1.citysearch.com.citysearch.com.(ns1,ns2,ns3).citygrid.com.
8aws1pvipcsp1.csprod.ctgrd.com.com.(i,j,f,m,d,b,k,g,a,l,h,e,c).gtld-servers.net.
9aws1pvipcsp1.csprod.ctgrd.com.ctgrd.com.(ns2,ns3,ns1).citygrid.com.
10aws1pvipcsp1.csprod.ctgrd.com.csprod.ctgrd.com.ns-639.awsdns-15.net. ns-1788.awsdns-31.co.uk. ns-1473.awsdns-56.org. ns-373.awsdns-46.com.
11dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com.com.(e,j,m,l,b,a,f,k,c,d,i,h,g).gtld-servers.net.
12dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com.amazonaws.com.(u3,u4,u2,r1,r2,r3,u6,u5,r4,u1).amazonaws.com.
13dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com.us-east-1.elb.amazonaws.com.(ns-947,ns-934,ns-916,ns-927,ns-941,ns-944,ns-925,ns-935).amazonaws.com.
We pick k.root-servers.net, one of the 13 root servers (1), and ask it about citysearch3.com and learn that com is delegated to 13 name servers (2), so we ask m.gtld-servers.net where we learn that citysearch3.com is delegated to three name servers, including ns2.citygrid.com (3), so we ask that one where we see a CNAME from citysearch3.com to redir2.citysearch.com, so we have to start all over again. We already know that h.gtld-servers.net is authoritative for com (4) and ask it about redir2.citysearch.com and learn that citysearch.com is delegated to three name servers (5), so we ask ns2.citygrid.com and see a second CNAME from redir2.citysearch.com to cspxy-vip.citysearch.com. We start over for the third time and we already know that ns3.citygrid.com is authoritative for citysearch.com (6) and ask it about cspxy-vip.citysearch.com and see yet another CNAME from cspxy-vip.citysearch.com to cspxy-vip.aws1.citysearch.com. We have yet again to start all over and we already know that ns1.citygrid.com is authoritative for citysearch.com (7) and ask it about cspxy-vip.aws1.citysearch.com and see yet another CNAME from cspxy-vip.aws1.citysearch.com to aws1pvipcsp1.csprod.ctgrd.com. We have yet again to start all over and we already know that i.gtld-servers.net is authoritative for com (8) and ask it about aws1pvipcsp1.csprod.ctgrd.com and learn that ctgrd.com is delegated to three name servers (9), so we ask ns2.citygrid.com where we learn that csprod.ctgrd.com is delegated to four name servers, including ns-639.awsdns-15.net (10), so we ask that one and see yet another CNAME from aws1pvipcsp1.csprod.ctgrd.com to dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com. We have yet again to start all over and we already know that e.gtld-servers.net is authoritative for com (11) and ask it about dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com and learn that amazonaws.com is delegated to ten name servers (12), so we ask u3.amazonaws.com where we learn that us-east-1.elb.amazonaws.com is delegated to eight name servers, including ns-947.amazonaws.com (13), so we ask that one and get the following answer:

Authoritative answer

ANSWER for citysearch3.com.
citysearch3.com.86400 CNAME redir2.citysearch.com.
ANSWER for redir2.citysearch.com.
redir2.citysearch.com.86400 CNAME cspxy-vip.citysearch.com.
ANSWER for cspxy-vip.citysearch.com.
cspxy-vip.citysearch.com.60 CNAME cspxy-vip.aws1.citysearch.com.
ANSWER for cspxy-vip.aws1.citysearch.com.
cspxy-vip.aws1.citysearch.com.3600 CNAME aws1pvipcsp1.csprod.ctgrd.com.
ANSWER for aws1pvipcsp1.csprod.ctgrd.com.
aws1pvipcsp1.csprod.ctgrd.com.60 CNAME dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com.
ANSWER for dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com.
dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com.60 A50.17.193.27 dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com points to 50.17.193.27.
60 A54.243.99.239 dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com points to 54.243.99.239.
60 A50.17.244.129 dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com points to 50.17.244.129.
60 A54.243.82.144 dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com points to 54.243.82.144.
60 AAAA2406:da00:ff00:0:0:0:3211:f481 dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com points to 2406:da00:ff00:0:0:0:3211:f481.
60 AAAA2406:da00:ff00:0:0:0:36f3:63ef dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com points to 2406:da00:ff00:0:0:0:36f3:63ef.
60 AAAA2406:da00:ff00:0:0:0:36f3:5290 dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com points to 2406:da00:ff00:0:0:0:36f3:5290.
60 AAAA2406:da00:ff00:0:0:0:3211:c11b dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com points to 2406:da00:ff00:0:0:0:3211:c11b.

uk. com. net. org. co.uk. ctgrd.com. citygrid.com. amazonaws.com. awsdns-46.com. awsdns-56.org. awsdns-15.net. citysearch.com. awsdns-31.co.uk. citysearch3.com. ns2.citygrid.com. r3.amazonaws.com. root-servers.net. r4.amazonaws.com. r1.amazonaws.com. ns3.citygrid.com. u5.amazonaws.com. csprod.ctgrd.com. u4.amazonaws.com. u6.amazonaws.com. u1.amazonaws.com. r2.amazonaws.com. ns1.citygrid.com. u2.amazonaws.com. u3.amazonaws.com. gtld-servers.net. elb.amazonaws.com. a.root-servers.net. f.gtld-servers.net. h.root-servers.net. h.gtld-servers.net. g.root-servers.net. c.gtld-servers.net. m.root-servers.net. g.gtld-servers.net. e.gtld-servers.net. j.root-servers.net. i.gtld-servers.net. m.gtld-servers.net. k.gtld-servers.net. d.root-servers.net. d.gtld-servers.net. i.root-servers.net. l.root-servers.net. k.root-servers.net. b.gtld-servers.net. f.root-servers.net. c.root-servers.net. a.gtld-servers.net. b.root-servers.net. l.gtld-servers.net. j.gtld-servers.net. e.root-servers.net. aws1.citysearch.com. ns-373.awsdns-46.com. ns-916.amazonaws.com. ns-927.amazonaws.com. ns-941.amazonaws.com. ns-925.amazonaws.com. ns-947.amazonaws.com. ns-639.awsdns-15.net. ns-935.amazonaws.com. ns-934.amazonaws.com. ns-944.amazonaws.com. ns-1473.awsdns-56.org. redir2.citysearch.com. ns-1788.awsdns-31.co.uk. cspxy-vip.citysearch.com. us-east-1.elb.amazonaws.com. aws1pvipcsp1.csprod.ctgrd.com. cspxy-vip.aws1.citysearch.com. aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com. dualstack.aws1pvipcsp1-1813637082.us-east-1.elb.amazonaws.com.
whois uk
whois net
whois org
whois com
whois co.uk
whois ctgrd.com
whois citygrid.com
whois awsdns-46.com
whois awsdns-56.org
whois amazonaws.com
whois awsdns-15.net
whois citysearch.com
whois awsdns-31.co.uk
whois citysearch3.com
whois root-servers.net
whois gtld-servers.net


whois citysearch3.com
domain info api citysearch3.com

Citysearch3.com has no IP numbers (. We are missing the IP:s of two servers: cspxy-vip.citysearch.com and redir2.citysearch.com.

This hostname cnames to cspxy-vip.citysearch.com and redir2.citysearch.com.

Also check www.citysearch3.com.

Citysearch3.com uses the CNAME record redir2.citysearch.com only.

The three name servers b, d and e.ns.citysearch.com together

There are about thirty domains that use the three name servers b, d and e.ns.citysearch.com together, hereafter referred to as "name server group 1". All of those use the two IPv4 numbers 208.85.8.39 and 209.104.35.228 together (example: seattlecitysearch.com, stlouiscitysearch.com and nashville-citysearch.com ). All of them has 2 ipv4 addresses (example: neworleanscitysearch.com, utahcitysearch.com and austincitysearch.com ) and all of them point to the two IP numbers 208.85.8.39 and 209.104.35.228 together (example: nycitysearch.com, sanfranciscocitysearch.com and sanjosecitysearch.com ).

The two name servers d and e.ns.citysearch.com together

There are twelve domains that use the two name servers d and e.ns.citysearch.com together (but not b.ns.citysearch.com ), hereafter referred to as "name server group 2". Eleven of those use the primary name server d.ns.citysearch.com (example: citysearch6.com, citysearchgiveaway.com and sidewalk.com ) and ten of them are under the tld "com" (example: citysearch11.com, citysearchoffers.com and citysearchutah.com ).

The primary name server d.ns.citysearch.com only

Two thirds of the about fourty domains that use the primary name server d.ns.citysearch.com use name server group 1 (example: portlandcitysearch.com, tampabaycitysearch.com and philadelphiacitysearch.com ).

The name server e.ns.citysearch.com

Twelve of the about fourty domains that use the name server e.ns.citysearch.com use name server group 2 (example: citysearch9.com, citysearch.net and citysearchtogo.net ).

robtex on citysearch3.com
RBL listing of citysearch3.com
mnw
/

Other "citysearch3" domains: com

Alexa Web of Trust Google Safe Browsing McAfee SiteAdvisor Norton Safe Web AVG mnw