Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.FRedirect ChainAction3 redirect(s), 1438 ms totalFIX
https://dartmouth.edu
420 ms · HTTP/1.1
http://www.dartmouth.edu/
448 ms · HTTP/1.1
http://home.dartmouth.edu/
91 ms · HTTP/1.1
https://home.dartmouth.edu/
479 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://dartmouth.edu | 302 | 420 ms | HTTP/1.1 | |
| 2 | http://www.dartmouth.edu/ | 301 | 448 ms | HTTP/1.1 | Apache/2.4.37 (Red Hat Enterprise Linux) mod_perl/2.0.12 Perl/v5.26.3 |
| 3 | http://home.dartmouth.edu/ | 301 | 91 ms | HTTP/1.1 | cloudflare |
| 4 | https://home.dartmouth.edu/ | 200 | 479 ms | HTTP/1.1 | cloudflare |
See the visual redirect chain in the HTTP Probe tab →
Each redirect adds latency. Try to minimize the chain to 1 hop.
Redirect chain — each hop adds latency; combine into one redirect where possible.
Source: Google Search Central / web.dev
Redirect directly from https://dartmouth.edu to https://home.dartmouth.edu/
Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.
Source: web.dev
If permanent, use 301 instead.
302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.
Learn more ▾ ▴
Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).
Source: Google Search Central
DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
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
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.
Learn more ▾ ▴
A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.
Source: sitemaps.org / Google Search Central
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
# Roverbot is evil <http://www.roverbot.com>
User-agent: Roverbot
Disallow: /
User-agent: *
Disallow: /stats/
Disallow: /cgi-bin/
Disallow: /~cfolt/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BURL Variantswww/non-www, trailing slash, HTTP→HTTPSREVIEW
www / non-www
Preferred variant: non-www
HTTP → HTTPS
HTTP version does not redirect to HTTPS
BTLS Certificate Expiry & Recommendations52 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
A+DNS Records1 A records, 74 ms lookupPASS
| A | 129.170.224.138 |
| AAAA | — |
| CNAME | — |
| NS | a1-119.akam.net, a9-66.akam.net, a16-64.akam.net, a14-67.akam.net, a5-65.akam.net, a18-64.akam.net |
| MX | 5 dartmouth-edu.mail.protection.outlook.com |
| TXT | atlassian-domain-verification=FKEPBB7b61BuK3b/O0/7YFIGZVNRC/HIYeXEbm8gA59wkRo3Rb... bw=RY8AsLPKQdaN7c8rjN6ls8fK6rrBABwOZGtym6dLLTvb logmein-verification-code=d911c3c1-eeb1-4c38-a55e-da6f189ed059 rqz9jf4yv02sppyr211kbm1btbhz6v7b 137342631-6189184 boIuOYRNm52O4nm+5cmx03iN8/aS/0bhvilx2PXCHm5CPCBhVNRYM7R02oWvwLtM8nNOnKaBETibgGYb... wrike-verification=MjM2MTM0Njo4Mjk3MDEzMGRlYzA0NGY5NzExYTIxNmZkODY3NzEzOTg3MTg1Z... facebook-domain-verification=mw3sr9iiez87clr5be0mvqfrfv5pdq have-i-been-pwned-verification=3be50d4794d105ef5933f0a21cb9a79e openai-domain-verification=dv-RtsKPAcMrS3Flc99KVWLzqvf atlassian-sending-domain-verification=5d2b1e4e-53a2-41d8-9614-e1924cdde783 airtable-verification=b05674e8a09dd5e6c951dd312e88f950 atlassian-domain-verification=yxVV9fe5fSJIOzrg/2jvRHYUZqs2H7a30Ix6hYxrYddhWzGtHr... google-site-verification=hKllXvHgM-6kI7rUysmZs8XkZ8WYMAeZfm6u0A-Xkms SPF v=spf1 ip4:129.170.137.224/28 ip4:158.247.30.34 ip4:143.244.92.221 ip4:206.107.4... TXTdartmouth.eduecostruxure-it-verification=6d15177b-1edc-460a-99ab-093745c902af apple-domain-verification=ySlaII1ZaW4H3sDj duo_sso_verification=1molDJXEuY6lYJxqwmYsRBhbi1YwLKsf3P08ctWCcJcJV7NRzEwF9chzEw9... anthropic-domain-verification-t7z5b9=1fjJieecLkFZPdrWfFsxUCeBs amazonses:qibTWZp9Z8XB7Gtv1R4HLgdDjfPqFTY8Xz2g4CxP3DY= r8kFztnc9M0pNIuK8e6W4oNnwPlJ69yd1zxyw66fnYCgdZnHH39dTwkZhDBPicE7NXXsez+cln83J5cx... atlassian-domain-verification=o62Mi2eR+5iVieiLtkYit+SwOzBX3nCYUa0Dmrho8ssDgmmG27... google-site-verification=bkySuymASSMWSDwJS-imzROnABz01fMYdYkOrsfRQNo |
| 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.
A+Domain Intelligencedartmouth.edu — 40 years, 8 months old, hosted on DARTMOUTH-AS - Dartmouth College, USPASS
745 days
July 31, 2028
52 days
Issued by Internet2
40 years, 8 months
Registered March 3, 1986
Status unknown
Protects against DNS spoofing
DARTMOUTH-AS - Dartmouth College, US
ASN AS10755
129.170.224.138
Registrar unknown