Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DURL VariantsActionwww/non-www, trailing slash, HTTP→HTTPSFIX
www / non-www
Inconsistent — duplicate content risk
HTTP → HTTPS
HTTP version does not redirect to HTTPS
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 2542 ms totalREVIEW
https://nd.edu
1245 ms · HTTP/1.1
https://www.nd.edu/
1297 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://nd.edu | 301 | 1245 ms | HTTP/1.1 | nginx/1.28.0 |
| 2 | https://www.nd.edu/ | 200 | 1297 ms | HTTP/1.1 | Apache |
See the visual redirect chain in the HTTP Probe tab →
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BHTTP Probe TimingTotal 1266 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations241 days until leaf cert expires — 4 issues to addressREVIEW
Certificate validity
Recommended actions
- Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
- Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
- Enable DNSSEC on your domain for DNS spoofing protection
- Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
ADNS Records1 A records, 1330 ms lookupPASS
| A | 34.193.237.201 |
| AAAA | — |
| CNAME | — |
| NS | ns2.nd.edu, ns1.nd.edu |
| MX | 10 aspmx.l.google.com 50 alt2.aspmx.l.google.com 50 alt1.aspmx.l.google.com 100 alt3.aspmx.l.google.com 100 alt4.aspmx.l.google.com |
| TXT | google-site-verification=E0Ai-zLdeN4kaVMLOAc3Hu8YxFfFwgkF-aqT137FID4 adobe-idp-site-verification=e9756968-501f-480d-8792-c63fdd9f80b1 google-site-verification=VFb81m0OmJ-cARBgKvmos2DsQWjrDVfR2YHlgeSm6Ug pardot_219862_*=7348adfdbfbbbc2208e360e007f11cc488ecadad55ac777bb7637bc1b722ecfa heroku-domain-verification=5bpsmgqd0irdsecvtkii8e9d0zwp33uszd4byfb6o _globalsign-domain-verification=LfgPuNnZOviHJVkLDsAnTjpDsFtY_T0pkBgmNG2dZs SPF v=spf1 include:_u.nd.edu._spf.smart.ondmarc.com ~all apple-domain-verification=bxq6rLIsclw0WUwj google-site-verification=JXLaLTpEQJNaOc47L5FCQMVzJswWy6oya8UgaRQWVE0 docusign=4909212b-a9ae-414a-8ac1-14ba8514c57a google-site-verification=emH8XyxZNPm54EgNuh42J5Kyer3hHpX4JkI_jGz021w docusign=13014d02-9888-4d97-ab61-75927ac9c354 atlassian-domain-verification=mcMH5cJpZFK46YS3U01Da6PVucaF3qS2ZMJa8/su7W8Xzl8omW... e2ma-verification=mancb cisco-ci-domain-verification=3b0cf87da3d06f5c131277db55b48ff9297a55db1ee0bcfc31a... d365mktkey=Y0fJCCYFQq9W2xqRIZO0D6DZUHtXPhcbITS81wsagm8x d365mktkey=W2RPNDEQGAox3gYW5Mr5AurRGPHiWglb63Cpbg43rogx e2ma-verification=q8fcb sendinblue-code:1a6818adbe852c76491242a60b3d2fe0 amazonses:TZOspN3D6KpXYYEvedb9ijMRaZZv9wIk2lVa2XS1zm4= wpe-verification=godandgoodlife _bikl4z8rqnwnpe44rum3006dh12popr brevo-code:f9880e3ab3b7e746b2db0ecf9f209a34 google-site-verification=jn_-65L7qcWLZmEo5JD4cyl6_w0YAOOdxzysOqHUtjo airtable-verification=1b0cc7a6fea2adca0106d9dc83226b8a openai-domain-verification=dv-1yKm9SGYfvIyOeIuWZH9XWie asv=e22f8141a541b5d2b0c634b621241be0 jamf-site-verification=ZezyIaoN2uwt0pCuh-8Saw |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.
Learn more ▾ ▴
Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.
Source: SRE practice / DNS architecture
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.
Slow DNS adds latency to every page load. Consider a faster DNS provider.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+Crawlabilityrobots.txt present, sitemap with 43 URLsPASS
Sitemap: https://www.nd.edu/sitemap.xml
User-agent: *
Disallow: /assets/css/
Disallow: /assets/features/
Disallow: /assets/js/
Disallow: /cache/
Disallow: /error/
Disallow: /offline/
A+Domain Intelligencend.edu — 38 years, 4 months old, hosted on AWSPASS
15 days
July 31, 2026
241 days
Issued by Internet2
38 years, 4 months
Registered July 7, 1988
Status unknown
Protects against DNS spoofing
AWS
ASN AS14618
34.193.237.201
Registrar unknown
Expiry timeline
Recommended actions
- Renew the domain or enable auto-renewal to prevent accidental expiry