No, definitely not a dumb question. It's a pretty specialized task.

If you're on Windows, open up a Command Prompt (easiest way to do that is to use the run command and enter "cmd"). Once that's up, type:

tracert www.robotkingdom.com

If you're on a Mac (or other *nix based system), open up Terminal and type:

traceroute www.robotkingdom.com

My output looks sort of like this:

traceroute to robotkingdom.com (182.239.48.57), 64 hops max, 52 byte packets
1 10.0.2.1 (10.0.2.1) 0.844 ms 0.555 ms 0.550 ms
2 router.firefly.private (192.168.58.254) 60.235 ms 96.994 ms 99.715 ms
3 loopback1.cha24.brisbane.telstra.net (165.228.7.1) 25.180 ms 27.955 ms 25.538 ms
4 tengige0-8-0-2.cha-core4.brisbane.telstra.net (203.50.51.1) 27.644 ms 26.733 ms 26.247 ms
5 pos0-4-1-0.ken-core4.sydney.telstra.net (203.50.6.205) 43.280 ms 44.221 ms 44.252 ms
6 bundle-ether1.pad-gw2.sydney.telstra.net (203.50.6.29) 42.215 ms 43.958 ms 44.236 ms
7 tengigabitethernet2-0.sydp-core02.sydney.reach.com (203.50.13.50) 45.903 ms 45.574 ms 44.591 ms
8 i-0-3-4-0.sydp-core05.bi.reach.com (202.84.221.221) 45.062 ms 44.492 ms 43.395 ms
9 i-15-1-0.hkhh-core01.bx.reach.com (202.84.143.173) 159.656 ms 160.591 ms 160.451 ms
10 i-9-0-3.tmh-core04.bi.reach.com (202.84.155.181) 158.090 ms 157.947 ms 158.002 ms
11 i-10-0-0.hkth01.bi.reach.com (202.84.153.238) 159.444 ms 157.940 ms 158.078 ms
12 peer.hgc.com.hk (218.189.96.53) 160.288 ms 159.522 ms 159.790 ms
13 218.189.101.122 (218.189.101.122) 159.332 ms 159.807 ms 160.129 ms


If it gets to a point where it's just spitting out asterisks, just cancel it (Ctrl-C) and paste as far as it got up to.

If you do that, we can see if and where there's a network blockage.