![\"whois\"](\"http:\/\/streamingradioguide.com\/startingover\/wp-content\/uploads\/2014\/10\/whois.png\")
<\/a><\/p>\n(Note the thumbnail of the page which I added recently but didn’t tell about in the blog)<\/p>\n
Since I’m not asking you to do research until you’ve had significant experience, this new feature is mainly here for my use (and the curious among you).<\/p>\n
First, some technical information.<\/p>\n
To get a web site visible, there are three different things that have to be done. In many cases, the same company provides all of them, but not always.<\/p>\n
The first is the Domain Registration<\/strong>. The domain registration process assigns exclusive use to a domain name on the internet – not only web servers, but email and other things you probably don’t want to know about. The process also provides a mechanism for resolving disputes where more than one person claims the same or similar names, or the name is a trademark. If I were to try to register Xerox.info, Xerox’s lawyers would challenge the registration and win.<\/p>\n The second thing you need is a web server<\/strong> on the internet, which is connected to the internet by someone who provides internet services and a path to reach the server. The current “investigate risk” link is telling you that information – which provides clues like server is located somewhere other than where you would expect (like Japan or Switzerland). It doesn’t mean there is an actual risk, but there is reason for being careful.<\/p>\n The third thing you need is a DNS resolver service<\/strong>. It’s the glue that holds the first two together. StreamingRadioGuide.com is registered, and the server is located at address 50.116.19.46.<\/p>\n When you try to access the server, first the domain is looked up to find out where to find the server. You will see that the domain is owned by me, and ENOM is the registrar (that’s the company in Chicago that used to house the web site). It tells you that my DNS lookup service is provided by EasyDNS, a company I switched to when ENOM’s DNS service failed and my business was losing $100s an hour because of it (back in the FindAnISP.com days). EasyDNS is located in Toronto, Canada.<\/p>\n The EasyDNS server tells the world that if you want to connect to StreamingRadioGuide.com, try IPv4 Address 50.116.19.46 or better yet, try IPv6 address 2400:cb00:2049:1::c629:defe<\/p>\n All of this is magic, and the good thing is you don’t need to understand anything I just said to use the World Wide Web \ud83d\ude42<\/p>\n So let’s say you’re trying to figure out if http:\/\/www.lagiganteradio.net\/ is really<\/em><\/strong> the website for WKIQ-AM (1240) in Eustis Florida, airing the Regional Mexican music format (The Big One).<\/p>\n The whois query will return to you:<\/p>\n Domain Name: LAGIGANTERADIO.NET Registration Service Provided By: SOLO10.COM S.A.<\/p>\n So the Domain Registrar is in Europe, DNS Server is located in Spain\u00a0\u00a0 (Espana), and the “Owner” of the domain is an individual named Javier Sanchez who lives in Guadalajara, Mexico.<\/p>\n So where is the actual server located?\u00a0\u00a0 doing a DNS lookup says the server is at an IP address controlled by a company in Lithuania, but the server is probably in England.\u00a0\u00a0 Doing a traceroute confirms this:<\/p>\n raceroute to 31.220.16.195 (31.220.16.195), 30 hops max, 60 byte packets The actual server is located in Manchester, England – the connection hops on some fiber cable in Northern Virginia (near the CIA) to get to Amsterdam in the the Netherlands, then over to England on a connection run by the Nippon Telephone and Telegraph.<\/p>\n So with all that information, is this the real web site or a fake copy?<\/p>\n [The above should convince you why the United States no longer is “in charge” of the Internet]<\/p>\n","protected":false},"excerpt":{"rendered":" For those doing station verification, a new link has been added to click to do a “Whois” query. (Note the thumbnail of the page which I added recently but didn’t tell about in the blog) Since I’m not asking you … Continue reading
\nRegistry Domain ID: 1643786752_DOMAIN_NET-VRSN
\nRegistrar WHOIS Server: whois.publicdomainregistry.com
\nRegistrar URL: www.publicdomainregistry.com<\/span>
\nUpdated Date: 2014-04-04T18:31:40Z
\nCreation Date: 2011-03-05T14:39:10Z
\nRegistrar Registration Expiration Date: 2016-03-05T14:39:10Z
\nRegistrar: PDR Ltd. d\/b\/a PublicDomainRegistry.com
\nRegistrar IANA ID: 303
\nRegistrar Abuse Contact Email:
\nRegistrar Abuse Contact Phone: +1-2013775952
\nDomain Status: clientTransferProhibited
\nRegistry Registrant ID: DI_14714404
\nRegistrant Name: javier sanchez
\nRegistrant Organization: javier sanchez
\nRegistrant Street: bahia s n
\nRegistrant City: guadalajara
\nRegistrant State\/Province: jalisco
\nRegistrant Postal Code: 44100
\nRegistrant Country: MX<\/span>
\nRegistrant Phone: +0.521331363205
\nRegistrant Phone Ext:
\nRegistrant Fax:
\nRegistrant Fax Ext:
\nRegistrant Email:
\nRegistry Admin ID: DI_14714404
\nAdmin Name: javier sanchez
\nAdmin Organization: javier sanchez
\nAdmin Street: bahia s n
\nAdmin City: guadalajara
\nAdmin State\/Province: jalisco
\nAdmin Postal Code: 44100
\nAdmin Country: MX
\nAdmin Phone: +0.521331363205
\nAdmin Phone Ext:
\nAdmin Fax:
\nAdmin Fax Ext:
\nAdmin Email:
\nRegistry Tech ID: DI_14714404
\nTech Name: javier sanchez
\nTech Organization: javier sanchez
\nTech Street: bahia s n
\nTech City: guadalajara
\nTech State\/Province: jalisco
\nTech Postal Code: 44100
\nTech Country: MX
\nTech Phone: +0.521331363205
\nTech Phone Ext:
\nTech Fax:
\nTech Fax Ext:
\nTech Email:
\nName Server: ns1.hostinger.es<\/span>
\nName Server: ns2.hostinger.es
\nName Server: ns3.hostinger.es
\nName Server: ns4.hostinger.es
\nDNSSEC:Unsigned<\/p>\n
\n1\u00a0 192.168.1.1 (192.168.1.1)\u00a0 0.271 ms\u00a0 0.237 ms\u00a0 0.246 ms
\n2\u00a0 * * *
\n3\u00a0 * * *
\n4\u00a0 cpe-024-074-xxx-xxx.carolina.res.rr.com (24.74.xxx.xxx)\u00a0 29.863 ms\u00a0 29.932 ms\u00a0 30.003 ms
\n5\u00a0 cpe-024-074-xxx-xxx.carolina.res.rr.com (24.74.xxx.xxx)\u00a0 17.143 ms\u00a0 17.488 ms\u00a0 17.566 ms
\n6\u00a0 be32.drhmncev01r.southeast.rr.com (24.93.64.200)\u00a0 23.047 ms\u00a0 17.461 ms\u00a0 17.310 ms
\n7\u00a0 bu-ether14.atlngamq46w-bcr00.tbone.rr.com (66.109.6.82)\u00a0 28.570 ms bu-ether44.atlngamq46w-bcr00.tbone.rr.com (107.14.19.46)\u00a0 32.564 ms bu-ether14.atlngamq46w-bcr00.tbone.rr.com (66.109.6.82)\u00a0 32.437 ms
\n8\u00a0 ae-1-0.pr0.atl20.tbone.rr.com (66.109.6.177)\u00a0 29.844 ms\u00a0 29.629 ms\u00a0 29.692 ms
\n9\u00a0 216.156.108.97.ptr.us.xo.net (216.156.108.97)\u00a0 32.125 ms\u00a0 32.189 ms 216.156.108.45.ptr.us.xo.net (216.156.108.45)\u00a0 27.108 ms
\n10\u00a0 67.111.23.95.ptr.us.xo.net (67.111.23.95)\u00a0 38.045 ms\u00a0 26.995 ms\u00a0 25.877 ms
\n11\u00a0 ae-1.r04.atlnga05.us.bb.gin.ntt.net (129.250.5.189)\u00a0 114.028 ms\u00a0 120.198 ms\u00a0 117.946 ms
\n12\u00a0 ae-8.r20.asbnva02.us.bb.gin.ntt.net (129.250.5.214)\u00a0 31.050 ms\u00a0 28.193 ms\u00a0 38.858 ms
\n13\u00a0 ae-0.r21.asbnva02<\/span>.us.bb.gin.ntt.net (129.250.4.5)\u00a0 39.650 ms\u00a0 27.401 ms *
\n14\u00a0 * ae-2.r23.amstnl02<\/span>.nl.bb.gin.ntt.net (129.250.2.145)\u00a0 116.540 ms\u00a0 125.581 ms
\n15\u00a0 ae-1.r03.amstnl02.nl.bb.gin.ntt.net (129.250.2.147)\u00a0 130.375 ms\u00a0 113.548 ms\u00a0 184.336 ms
\n16\u00a0 83.231.213.194 (83.231.213.194)\u00a0 140.291 ms\u00a0 131.805 ms\u00a0 166.202 ms
\n17\u00a0 te-9-3-3346.core-dc1.man4.uk.m247.com (77.243.185.177)\u00a0 151.784 ms\u00a0 142.160 ms\u00a0<\/span> 145.958 ms
\n18\u00a0 176.10.80.150 (176.10.80.150)\u00a0 205.378 ms\u00a0 155.228 ms\u00a0 136.225 ms<\/p>\n