cox blocking integrisandme.com
phone with wifi on, no. Phone with wifi off, yes. All computers on wifi: no
Traceroute:
traceroute to integrisandme.com (204.107.242.158), 30 hops max, 60 byte packets 1 _gateway (192.168.1...
Forum Discussion
Tracing route to integrisandme.com [104.18.24.199]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 5 ms 15 ms 9 ms x.x.x.x Security reasons
3 9 ms 10 ms 10 ms 100.127.40.254
4 10 ms 5 ms 5 ms 100.120.124.20
5 14 ms 15 ms 18 ms ashbbprj01-ae2.rd.as.cox.net [68.1.0.242]
6 15 ms 15 ms 14 ms 68.105.30.114
7 16 ms 17 ms 11 ms 172.70.32.4
8 14 ms 15 ms 15 ms 104.18.24.199
Using the IP you were tracing -
Tracing route to integrishealthandme.com [204.107.242.158]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms www.routerlogin.com [192.168.1.1]
2 9 ms 9 ms 9 ms x.x.x.x -Security reasons
3 6 ms 4 ms 7 ms 100.127.40.254
4 9 ms 8 ms 9 ms 100.120.124.20
5 45 ms 48 ms 45 ms mtc3dsrj02-ae1.rd.ok.cox.net [68.1.0.109]
6 * * 46 ms 100.121.188.1
7 47 ms 49 ms 47 ms COX-24-249-237-42-static.coxinet.net [24.249.237.42]
8 * * * Request timed out.
9 54 ms 53 ms 53 ms integrishealthandme.com [204.107.242.158]
No problems getting there. tray again? before trying, do from an administrative command prompt
ipconfig /flushdns
Getting there is hit or miss. Sometimes just shows a background image sometimes I get "integrishealthandme.com took too long to respond." On FIOS too using Google DNS so not a Cox problem. Tried changing from google DNS to Cloudflare DNS, no change. Tried disabling IPv6. No change. My guess is they changed their site and it hasn't propagated yet. I tried looking for the Whois contact but it's masked. I suggest trying from a VPN. Used Opera GX VPN and it worked.
Non-authoritative answer:
Name: integrisandme.com
Addresses: 2606:4700::6812:18c7
2606:4700::6812:19c7
104.18.24.199
104.18.25.199
Pinging integrisandme.com [104.18.25.199] with 32 bytes of data:
Reply from 104.18.25.199: bytes=32 time=12ms TTL=56
Reply from 104.18.25.199: bytes=32 time=9ms TTL=56
Reply from 104.18.25.199: bytes=32 time=10ms TTL=56
Reply from 104.18.25.199: bytes=32 time=11ms TTL=56
Ping statistics for 104.18.25.199:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 12ms, Average = 10ms
1 <1 ms <1 ms <1 ms RT-AX86U-22F8 [192.168.50.1]
2 4 ms 2 ms 4 ms lo0-100.PRVDRI-VFTTP-304.verizon-gni.net [100.40.77.1]
3 9 ms 7 ms 3 ms B3304.PRVDRI-LCR-21.verizon-gni.net [100.41.129.50]
4 * * * Request timed out.
5 * * * Request timed out.
6 13 ms 9 ms 14 ms 162.158.152.3
7 11 ms 12 ms 8 ms 104.18.25.199
That's why I suggested they do a flushdns. It appears to have propagated but if their cache is holding on tot he old info, they could have an issue. I was able to use chrome, edge, safari and opera, (with and without internal vpn) without issue from here in Va.
I flushed my DNS(after changing my DNS too) and still couldn't get to the site so I think it will take more then that. I think your area has the routing correctly while mine and OPs is not.
hmmm. def sounds like you hit the nail on the head, dns not finished updating from the root servers all over.
