Skip to content
https://getty.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
1
REVIEW
5
PASS
3
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
3 PASS 5 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.

B
Redirect Chain
1 redirect(s), 1167 ms total
REVIEW
1 redirect(s), 1167 ms total
Info::
Single redirect
Got: https://getty.edu → https://www.getty.edu/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://getty.edu
Warning::
Redirect overhead: 1167 ms total
Got: 1167 ms

https://getty.edu

676 ms · HTTP/1.0

302

https://www.getty.edu/

491 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://getty.edu302676 msHTTP/1.0BigIP
2https://www.getty.edu/200491 msHTTP/1.1

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

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: 251 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 251 B Sitemaps referenced 0 User-agents SortSite, *, AhrefsBot, Yeti Blocking No — crawling allowed
# /robots.txt

User-agent: SortSite
Allow: /

User-agent: *
Disallow: /cgi-bin

User-agent: AhrefsBot
Disallow: /

User-agent: *
Disallow: /slampoets

User-agent: *
Disallow: /research/collections/mirador/

User-agent: Yeti
Disallow: /art/collection/

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

C
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.getty.edu/
200https://getty.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://getty.edu/ https://www.getty.edu/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

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

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 Records
1 A records, 38 ms lookup
PASS
1 A records, 38 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 153.10.241.9
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1831.awsdns-36.co.uk, ns-1423.awsdns-49.org, ns-776.awsdns-33.net, ns-217.awsdns-27.com
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: 38 ms
Got: 38 ms
A153.10.241.9
AAAA
CNAME
NSns-1831.awsdns-36.co.uk, ns-1423.awsdns-49.org, ns-776.awsdns-33.net, ns-217.awsdns-27.com
MX
0 getty-edu.mail.protection.outlook.com
TXT
airtable-verification=f7df56a062fffa9c8f260a1201709ac9
docusign=9c5948e3-b525-41b1-b637-25a9251599a0
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
docusign=e3a421d8-0885-4a4c-9ef8-24e16884db80
KGIDZFCHW4HWXFY5D42AN2H67CVYKHJRH6GMVIKQR
ZOOM_verify_bwNutJMbTWqJYD3JQEb0pg
MS=ms61943381
klaviyo-site-verification=U3W8N9
jamf-site-verification=HAHX5wcc7-mpRLBA_77uJg
apple-domain-verification=Az89cFMGmZ1lgYYY
facebook-domain-verification=1xdfvph90fchv9lno1xckdgmzt5xub
google-site-verification=5ZXxmdOKXxQaia4fFm2VBvsBZE54tlYBL0SB7Sz1RQ0
@=proxy-ssl.webflow.com
shopify-verification-code=wZ5qJD1z7ftulSNeprotAWMHDcd66M
ccisso=7dbbe59e-d867-4dcc-85e3-f5cc52283155
CAALookup not available with standard resolver
Resolved in 38 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
getty.edu — 34 years, 5 months old, hosted on JPGT-22063 - J. Paul Getty Trust, US
PASS
getty.edu — 34 years, 5 months old, hosted on JPGT-22063 - J. Paul Getty Trust, US
Info::
Domain registered until Jul 31, 2028 (2 years, 3 months remaining)
Info::
Hosting: JPGT-22063 - J. Paul Getty Trust, US
Got: AS22063
Domain expiry

744 days

July 31, 2028

SSL certificate

129 days

Issued by Internet2

Domain age

34 years, 5 months

Registered April 29, 1992

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

JPGT-22063 - J. Paul Getty Trust, US

ASN AS22063

153.10.241.9

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created April 29, 1992 (34 years, 5 months ago)
Expires July 31, 2028 (2 years, 3 months)
Last Updated September 4, 2025
Name Servers ns-1423.awsdns-49.org, ns-1831.awsdns-36.co.uk, ns-776.awsdns-33.net, ns-217.awsdns-27.com
Registrant The J. Paul Getty Trust
Hosting
IP Address 153.10.241.9
ASN AS22063 (JPGT-22063 - J. Paul Getty Trust, US)
Provider JPGT-22063 - J. Paul Getty Trust, US
Data source: whois (1.0s)
A
HTTP Probe Timing
Total 744 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
36 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
176 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
356 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
745 ms
Total Time Total request time from DNS lookup through full response.
745 ms

Connection waterfall

DNS Lookup 36 ms TCP Connect 176 ms TLS Handshake 356 ms Server Processing 176 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