cox blocking integrisandme.com

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. 

I dug this up. Don't fully understand it but looks like the DNS record will expire in 7 days. Does that mean it should fix itself in a week?

primary name server = adele.ns.cloudflare.com
responsible mail addr = dns.cloudflare.com
serial = 2315394902
refresh = 10000 (2 hours 46 mins 40 secs)
retry = 2400 (40 mins)
expire = 604800 (7 days)
default TTL = 1800 (30 mins)

DNS is set to a one week refresh, 

Your SOA serial number is: 2315394902. This can be ok if you know what you are doing. This is an alert

Also While there are no direct PTR records, there are reverse ptr records - 

The DNS records for this site, ore actually kinda hinky....

Where did you get that Info? MXtoolbox is usually reliable. I found this as a definition of a PTR.

The reverse DNS record (rDNS) is also known as the PTR record, pointer record, or IP resolver. A PTR is a reverse record for an IP address that allows an IP to map to a domain and vice versa.

Couldn't find any mention of a reverse PTR.

intodns.com

Trust me, I know ALL about DNS. In the 90's I worked directly with Microsoft setting up 2 Servers with ½ a class c license for a Dial up ISP. Windows NT 4.0 was not designed to handle half a class c dns file, and each entry had to be hand edited. I was walking the halls muttering DNS under my breath for a week. 

Doesn't that show the PTR for the MX record IP, not the PTR for the A record's IP address. Please, educate me. I used to update and manage DNS records at Cox Business. Part of the training was going over how DNS works so i have a decent understanding but there is always room to grow.

Literally a copy and paste from that page. It's used in reverse DNS lookup