Skip to content
https://punahou.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 4 REVIEW 2 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 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.punahou.edu/
200https://punahou.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://punahou.edu/ http://www.punahou.edu/

HTTP version does not redirect to HTTPS

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.

B
Redirect Chain
1 redirect(s), 1305 ms total
REVIEW
1 redirect(s), 1305 ms total
Info::
Single redirect
Got: https://punahou.edu → https://www.punahou.edu/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1305 ms total
Got: 1305 ms

https://punahou.edu

299 ms · HTTP/1.1

301

https://www.punahou.edu/

1007 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://punahou.edu301299 msHTTP/1.1nginx
2https://www.punahou.edu/2001007 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

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: 129 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 129 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /podium
Allow: /podium/default.aspx*
Disallow: /api
Disallow: /app$
Disallow: /app/
Disallow: /ftpimages

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

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

Recommended actions

  • Renew certificate — 30 days remaining
  • 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 Records
1 A records, 56 ms lookup
PASS
1 A records, 56 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 54.209.77.18
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: pdns03.domaincontrol.com, pdns04.domaincontrol.com
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: 56 ms
Got: 56 ms
A54.209.77.18
AAAA
CNAME
NSpdns03.domaincontrol.com, pdns04.domaincontrol.com
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
workplace-domain-verification=I2n4yKiVJRZZ9bYzNfEAlXrKF3VooI
SPF v=spf1 ip4:204.107.82.0/24 include:_spf.google.com include:_spf.paubox.com inclu...
MS=ms53100650
ciscocidomainverification=398145002e55ca864cfcb1a74d217dc463ae5fd1631d57aa1f5d3f...
google-site-verification=DiYkGuc0YwxWrppOEE2MfkQ4lMtJte2dGOZp4a5QLm0
include:_spf.atlassian.net
google-site-verification=NTqGemT5jARx9WraQiej-mwB8-2w8Aj2UPKL8n44OGs
adobe-idp-site-verification=3bad3f4fc9d4d94294298ec399e39e7945c46b02299fc66fd7f9...
fhghrsdg7lrm4oh20i4gipt6q7
efl3cuojq1nu1cu10qm3mgt7lh
openai-domain-verification=dv-orxJ4p1ywUtO03eeicoS8kHs
ecostruxure-it-verification=96f5f6a6-5e42-420a-be89-13d79855af56
intersight=dd58eb059829a92556deef6e542244015f228e6af3ada47a8a64fd6d7c851908
ar4i50v329f32dv799ev7b4a65
IMYWJT6P7GOEZHGU5KFRXTRUQ24GL6UCXZSHZG13C
atlassian-sending-domain-verification=de3ff897-8387-4520-a303-aae1912c92cd
apple-domain-verification=c2nYAfm5umut4vpm
cikhg8uoeftfq91sm99ibrmu5v
jamf-site-verification=RCq_Nhjy46IAVzE1xzY4PA
624cjgk0gp1vt770bj2ssmo7p9
CAALookup not available with standard resolver
Resolved in 56 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+
Domain Intelligence
punahou.edu — 31 years, 5 months old, hosted on AWS
PASS
punahou.edu — 31 years, 5 months old, hosted on AWS
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: AWS
Got: AS16509
Domain expiry

19 days

July 31, 2026

SSL certificate

30 days

Issued by Let's Encrypt

Domain age

31 years, 5 months

Registered April 30, 1995

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

54.209.77.18

Registrar

Registrar unknown

Lock status unknown 2 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 April 30, 1995 (31 years, 5 months ago)
Expires July 31, 2026 (3 months)
Last Updated July 8, 2025
Name Servers pdns03.domaincontrol.com, pdns04.domaincontrol.com
Registrant Punahou School
Hosting
IP Address 54.209.77.18
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (1.5s)
A+
HTTP Probe Timing
Total 354 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
54 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.
101 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
355 ms
Total Time Total request time from DNS lookup through full response.
355 ms

Connection waterfall

DNS Lookup 54 ms TCP Connect 100 ms TLS Handshake 101 ms Server Processing 99 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