Receiving "site can't be reached, the connection was reset" and "Web Page Blocked" messages when trying to open custom domain for site but can open the default netlify one just fine

the netlify site name is nghpitt.netlify.app, and the actual site name im trying to open is nghpitt.com. it doesnt open ever when i try the custom domain name!! or when i try www.nghpitt.com. at first it did open, but on certain networks, now it doesnt open at all and i only get security warnings

Hi your site is now resolving with a certificate as well. Are you still experiencing this issue?

it does open on some networks now, but now the custom domain specifically doesnt open on my university network and i contacted them and they said the issue is from netlify

Based on a quick look at DNS records @manalbouk, I suspect the records for nghpitt.com are incorrect or incomplete. Can you share a screenshot of the records you see for this domain in Netlify?

Hi, @manalbouk. If the domain only does not work on the university network that strongly suggested the root cause is the university network and not at Netlify.

If they think the root cause is Netlify, what is their evidence of this? I ask because that simply does not make any sense and without proof it just sounds like someone avoiding doing work they do not want to do.

Again, if they blame Netlify, they must have proof of this. If they have proof, please share it here.

Would you be willing to please do a test for me? If so, please do the following. Please also note that this test must be done using the university network when the errors are occurring.

  1. (these first two steps can be done anywhere - they do not require the university network) install the CLI tool dig on the system that gets the error - DigitalOcean has a great guide on this here
  2. install the CLI tool curl (link to instructions)
  3. this step requires the university network - on the affect system run this dig command: dig nghpitt.com
  4. this step requires the university network - run this command: curl --compressed -svo /dev/null --stderr - -k https://nghpitt.com/
  5. Post the complete output of both commands from steps 3 and 4 here in a reply post

If you do so, that will likely tell us the cause of the issue and we can provide next steps based on what we discover.