HTTPS over IPv6· not part of the grade yet The certificate served over IPv6 at 2620:12a:8001::3 isn't valid for virginia.edu: ERR_TLS_CERT_ALTNAME_INVALID.
https://virginia.edu/ via 2620:12a:8001::3· ERR_TLS_CERT_ALTNAME_INVALID
problem
What's keeping virginia.edu from an A
www.virginia.edu is an alias of 44.77.148.132.host.secureserver.net, which has no IPv6 www.virginia.edu is a CNAME, so it can't also have its own AAAA record. Ask whoever runs 44.77.148.132.host.secureserver.net to enable IPv6 there — or replace the alias with the A and AAAA records they give you. Why some hosts don't offer IPv6
The certificate served over IPv6 is wrong The certificate served over IPv6 at 2620:12a:8001::3 isn't valid for virginia.edu: ERR_TLS_CERT_ALTNAME_INVALID. Often the IPv6 address points at a different server (or an old one) than IPv4 does. Make sure 2620:12a:8001::3 serves the same certificate as your IPv4 address.
Mail servers without IPv6 tm.az.virginia.edu has no AAAA record, so mail from IPv6-only servers can't reach it directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.
Nameservers without IPv6 uvaarpa.virginia.edu, eip-01-aws.net.virginia.edu, nom.virginia.edu all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.