Skip to content
https://lehigh.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
Crawlability
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 113 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 113 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# robots.txt for http://www.lehigh.edu/~  -- blank disallow means allow all - 2007-01-26
User-agent: *
Disallow:

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
TLS Certificate Expiry & Recommendations
227 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

227
days left
0d 30d 60d 90d+

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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 Records
1 A records, 118 ms lookup
PASS
1 A records, 118 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.180.1.81
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: dns3.lehigh.edu, dns1.lehigh.edu, dns2.lehigh.edu
Info::
5 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: 118 ms
Got: 118 ms
A128.180.1.81
AAAA
CNAME
NSdns3.lehigh.edu, dns1.lehigh.edu, dns2.lehigh.edu
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
MS=ms42681240
SPF v=spf1 ip4:128.180.0.0/16 include:_spf.google.com include:spf.elluciancloud.com ...
docusign=43c03dab-30ab-430c-8d89-3ffa6d41ce7f
anthropic-domain-verification-24a42b=49AX9zgxLnCYiqpETqxu0l1A9
apple-domain-verification=IPiUR6GaqScXAI3Z
rhino_accounts=7ad5a6b3afa8271aae45d47a000c7f5d
google-site-verification=gezvJKSFmRwgEPdl0XmQxTOuWujAMfnWxoZi1MOryVQ
adobe-idp-site-verification=0d1529611e9911860e10ab80ad44dec37cda0cb662d6f61cafa5...
v=mozautoconfig1 url:http://www.lehigh.edu/mail/tb3.xml
docusign=24d1b057-4b13-4922-acdd-fb1b82d6b66c
4405b39ad7eb7a601eb42d89e48f8dc2f57676a388b1e92e20501bc57e980202
canva-site-verification=bYU4vUxaGyEHqjBHawhgMg
miro-verification=f690999e93503641cf1a5f808984b605178b47eb
CAALookup not available with standard resolver
Resolved in 118 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), 817 ms total
PASS
1 redirect(s), 817 ms total
Info::
Single redirect
Got: https://lehigh.edu → https://www2.lehigh.edu/ (302)
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://lehigh.edu
Info::
Redirect overhead: 817 ms total
Got: 817 ms
Info::
Cross-domain redirect detected

https://lehigh.edu

302 ms · HTTP/1.1

302

https://www2.lehigh.edu/

515 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://lehigh.edu302302 msHTTP/1.1Apache/2.4.66 (Debian)
2https://www2.lehigh.edu/200515 msHTTP/1.1Apache/2.4.66 (Debian)

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+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

302https://www.lehigh.edu/
200https://lehigh.edu/

Preferred variant: non-www

HTTP → HTTPS

301http://lehigh.edu/ https://lehigh.edu/

Consistent

A+
Domain Intelligence
lehigh.edu — 38 years, 7 months old, hosted on LEHIGH - Lehigh University, US
PASS
lehigh.edu — 38 years, 7 months old, hosted on LEHIGH - Lehigh University, US
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: LEHIGH - Lehigh University, US
Got: AS6522
Domain expiry

45 days

July 31, 2026

SSL certificate

227 days

Issued by GoDaddy.com, Inc.

Domain age

38 years, 7 months

Registered March 29, 1988

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

LEHIGH - Lehigh University, US

ASN AS6522

128.180.1.81

Registrar

Registrar unknown

Lock status unknown 3 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
Registrar
Created March 29, 1988 (38 years, 7 months ago)
Expires July 31, 2026 (3 months)
Last Updated July 10, 2025
Name Servers dns1.lehigh.edu, dns2.lehigh.edu, dns3.lehigh.edu
Registrant Lehigh University
Hosting
IP Address 128.180.1.81
ASN AS6522 (LEHIGH - Lehigh University, US)
Provider LEHIGH - Lehigh University, US
Data source: whois (1.1s)
A
HTTP Probe Timing
Total 422 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
116 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
100 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
105 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
423 ms
Total Time Total request time from DNS lookup through full response.
423 ms

Connection waterfall

DNS Lookup 116 ms TCP Connect 100 ms TLS Handshake 105 ms Server Processing 102 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