Skip to content
https://mit.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.mit.edu/
200https://mit.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://mit.edu/ http://web.mit.edu/

HTTP version does not redirect to HTTPS

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 199 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

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.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 199 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /afs/
Disallow: /cgi-bin/
Disallow: /user/
Disallow: /org/
Disallow: /activity/
Disallow: /contrib/
Disallow: /dept/
Disallow: /software/
Disallow: /bin/
Disallow: */Public/*

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
TLS Certificate Expiry & Recommendations
Action
14 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

14
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 14 days remaining
  • 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
B
CDN & Delivery
Akamai
REVIEW
Akamai
Info::
Site is served via Akamai CDN
Got: server header
CDN Detected: Akamai
Provider Akamai Evidence server header
A+
DNS Records
1 A records, 8 ms lookup
PASS
1 A records, 8 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 92.123.164.194
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:1180:183::255e, 2a02:26f0:1180:197::255e
Info::
8 nameserver(s) configured
Got: use2.akam.net, eur5.akam.net, use5.akam.net, asia2.akam.net, ns1-173.akam.net, ns1-37.akam.net, usw2.akam.net, asia1.akam.net
Info::
1 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 8 ms
Got: 8 ms
A92.123.164.194
AAAA2a02:26f0:1180:183::255e, 2a02:26f0:1180:197::255e
CNAME
NSuse2.akam.net, eur5.akam.net, use5.akam.net, asia2.akam.net, ns1-173.akam.net, ns1-37.akam.net, usw2.akam.net, asia1.akam.net
MX
100 mit-edu.mail.protection.outlook.com
TXT
E2MA-VERIFICATION=MONGB
google-site-verification=pqf9o422iIeT7mzfZmQwkpLYH3VTlB05OC9c_OncFOg
adobe-idp-site-verification=0817e32603f0dda03188b9f1f3bbaf4f754c5322926036af8890...
openai-domain-verification=dv-pavuNIk1XG88x99BoqSFI0Zs
*fastly-domain-delegation-hnb9joooe7gojgqu4eth-00494769-2025-08-23
1VNZ334aKc8FypCKDhIMOQBsKFd8gCgTFQuPlDwQfzPNxPCKonTOnhuFQ8+kE32E2TgkBiOp9EFab5nf...
E2MA-VERIFICATION=C8D4
amazonses:asyYfDTQj+TCy9t5jFbakgwGbomDqXREEs3KdC0iMQE=
E2MA-VERIFICATION=8AWBB
docusign=37fbdad0-5267-4b79-9402-ff9df7e9331f
pardot_310211_*=a4e9728d1b90355b6240f4d7778cc4da11c10a20552ae99e6ed03d8e48c06583
airtable-verification=46ae122907d40a1413b6a05898774435
E2MA-VERIFICATION=86JGB
stripe-verification=fe726543b783764b2ba9137f4e675faa0709416ac7a5d9f50e21248a706a...
google-site-verification=b4-1loZHD1WzNmews_hsTTKL__gLblD6iKBFbA4j97c
e2ma-verification=oiiib
atlassian-domain-verification=maRNLIMivtdhvCr9JoVuLKHWRn7mZOY8072lyRNeyamz0NHc/s...
e2ma-verification=xiiib
AIRTABLE-VERIFICATION=C8040E640F7DEAB69A01D68C91893E07
google-site-verification=qNAffaSjUkhb2JCBb1BQ2nXAkcNYLeLc7G6vjMRD1js
mandrill_verify.28vVgPhRZLda1o_v90CPWg
docusign=78c4c36c-1180-44b1-b277-be9be4a08b73
airtable-verification=4283ac2aa983e97636807d478d6bf30c
atlassian-domain-verification=3eRva0Gy/EjVyKEw46uExfEXpDGJfhwocwVCy5NTxcPpf89Aqd...
include:4920340.spf07.hubspotemail.net
e2ma-verification=uviib
ecgkc7fnflsm01hh6uqjr86h02
e2ma-verification=piiib
SPF v=spf1 include:_s00430413.autospf.email -all
airtable-manual-domain-verification=ce83c94e-0127-4fd3-9265-3b37a46a7b8a
mgverify=2a07014ab707abf9b6f984210c05ef7a1fd905296aebe173776844c14db61c1e
atlassian-domain-verification=3Ex0JUvwojvbDLOJvNHnYUFEZCF+kwii0OjHbhDkymB97xpCOk...
google-site-verification=6ethhhET4cfz7L1Dfve9bCOTAqMr6IU79Va6gb8HxlA
CAALookup not available with standard resolver
Resolved in 8 ms

Multiple A records provide failover if one server goes down.

Why this matters

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.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A
Redirect Chain
1 redirect(s), 202 ms total
PASS
1 redirect(s), 202 ms total
Info::
Single redirect
Got: https://mit.edu → https://web.mit.edu/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://mit.edu
Info::
Cross-domain redirect detected

https://mit.edu

59 ms · HTTP/1.1

302

https://web.mit.edu/

142 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://mit.edu30259 msHTTP/1.1AkamaiGHost
2https://web.mit.edu/200142 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

If permanent, use 301 instead.

Why this matters

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

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:1180:183::255e, 2a02:26f0:1180:197::255e
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:1180:183::255e, 2a02:26f0:1180:197::255e Connection Reachable (1 ms)
A+
Domain Intelligence
mit.edu — 41 years, 5 months old
PASS
mit.edu — 41 years, 5 months old
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Domain expiry

17 days

July 31, 2026

SSL certificate

14 days

Issued by DigiCert Inc

Domain age

41 years, 5 months

Registered May 23, 1985

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

2a02:26f0:1180:197::255e

Registrar

Registrar unknown

Lock status unknown 8 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Renew the TLS certificate or verify auto-renewal is working
Registrar
Created May 23, 1985 (41 years, 5 months ago)
Expires July 31, 2026 (3 months)
Last Updated January 15, 2026
Name Servers asia2.akam.net, ns1-37.akam.net, ns1-173.akam.net, eur5.akam.net, use5.akam.net, usw2.akam.net, asia1.akam.net, use2.akam.net
Registrant Massachusetts Institute of Technology
Hosting
IP Address 2a02:26f0:1180:197::255e
Data source: whois (0.6s)
A+
HTTP Probe Timing
Total 14 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
4 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
14 ms
Total Time Total request time from DNS lookup through full response.
14 ms

Connection waterfall

DNS Lookup 4 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 5 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback