Unable to reach Snohomish County online bill pay site (snopay)

[SamInWa]

Has anyone else had this problem?  I've never been able to connect to the 

The link you get sent to from the https://www.snopud.com/ is below (I know it looks odd)

https://secure8.i-doxs.net/bdx/Default.aspx?BillerID=5HIAVXPIcm

Note a few things:

1. This has never worked for me at home (been here just over a month)
2. I can get to that site from work just fine (so it is up)
3. I've cleared out my browser cache, restarted my machine, reset my internet connection, etc.
4. I've tried IE, Chrome, Edge, and FireFox

At this point, I just am assuming that XFinity's network is blocking it or timing it out sonehow.

The error from Chrome is "ERR_CONNECTION_TIMED_OUT".

Anyone else every successfully gotten to Snohomish County's online pay site through Xfinity?

[Latoque]

I copied and pasted the first link you posted into my address bar and it takes me straight to this------------------

I'm using Chrome at the moment, Windows 10.  The URL in the address bar appears as---------

https://www.snopud.com/?p=1433

[BruceW]

---

@SamInWa wrote: ... I can get to that site from work just fine (so it is up) ...

---

I can reach the .i-doxs.net site. When one customer cannot reach a site but others can, it usually means the site is blocking that customer's public Comcast IP. The fact that you can reach the site from your work system reinforces this. You can look up your IP on your home system at https://www.google.com/search?q=IP. You'll need to ask the site's admins for help with this.

What does a trace to secure8.i-doxs.net show? In Windows, open a Command Prompt window, enter

    tracert -4 secure8.i-doxs.net

and post the output. Mine looks like:

Tracing route to secure8.i-doxs.net [205.216.45.38] over a maximum of 30 hops:

1 10 ms  2 ms   1 ms  router1 [192.168.1.1]
2 11 ms 10 ms 11 ms 96.120.9.181
3 11 ms   9 ms  9 ms te-0-6-0-0-sur02.york.pa.pitt.comcast.net [162.151.68.57]
4 11 ms 10 ms 10 ms 96.110.24.214
5 12 ms 10 ms 11 ms 96.110.25.65
6 18 ms 19 ms 19 ms be-34-ar01.mckeesport.pa.pitt.comcast.net [69.139.168.141]
7 26 ms 25 ms 27 ms be-7016-cr02.ashburn.va.ibone.comcast.net [68.86.91.25]
8    *        29 ms 27 ms be-1302-cs03.ashburn.va.ibone.comcast.net [96.110.32.177]
9 28 ms 35 ms 27 ms be-2307-pe07.ashburn.va.ibone.comcast.net [96.110.32.194]
10 28 ms 25 ms 25 ms dcx4-brdr-01.inet.qwest.net [65.120.84.65]
11     *           *           *        Request timed out.
12 66 ms 77 ms 66 ms 216.34.172.50
13 62 ms 62 ms 62 ms das1-v3008.dl2.savvis.net [216.34.164.62]
14 62 ms    *        63 ms 205.216.44.18
15-30  *      *           *        Request timed out.

Note that although the trace does not reach the target, it does reach beyond Comcast's network at hop #10. That tells us that Comcast is not blocking the site.