Skip to content
https://uga.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
302 Found
Checks
9
4 PASS 4 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), 1143 ms total
REVIEW
1 redirect(s), 1143 ms total
Info::
Single redirect
Got: https://uga.edu → https://www.uga.edu:443/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://uga.edu
Warning::
Redirect overhead: 1143 ms total
Got: 1143 ms

https://uga.edu

367 ms · HTTP/1.1

302

https://www.uga.edu:443/

776 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uga.edu302367 msHTTP/1.1awselb/2.0
2https://www.uga.edu:443/200776 msHTTP/1.1AmazonS3

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
URL Variants
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
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.uga.edu/
200https://uga.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://uga.edu/ → https://uga.edu:443/

Consistent

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

Certificate validity

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

Recommended actions

  • 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
2 A records, 676 ms lookup
PASS
2 A records, 676 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 3.33.229.187, 15.197.234.180
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns2.uga.edu, dns3.uga.edu
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
Warning::
DNS resolution is slow (676 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 676 ms
A3.33.229.187, 15.197.234.180
AAAA—
CNAME—
NSdns2.uga.edu, dns3.uga.edu
MX
10 uga-edu.mail.protection.outlook.com
TXT
brevo-code:59b3a18744d24f960bd78166f34f87c5
d365mktkey=YjcbfV14vrqxM23dyVvRxi8wEuaPmwFaxFkigxn2m58x
Foxit-domain-verification=45b5f5c2615965c20ca4aab810e74cb5
SPF v=spf1 include:_spf.mlsend.com include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ...
e2ma-verification=nr4ab
ms-domain-verification=deabb3d5-5c1a-4e57-b38e-98c74f1558b8
amazonses:H8rIXKMAw9ljXAiKFbQCELD15iE+XIEOQyX+oWMcGr8=
dfacb6fb-9598-4684-815e-c053426bab30
google-site-verification=zwncZ6G2jDsaF3OeQztWytnTzTz2WWPeKghso_jAPmI
openai-domain-verification=dv-LP1MjyPoR1m3TqgPu0l57YKm
atlassian-domain-verification=rZPHO8vvAWCWQbD8d3xvAqFOytZ/wDnX4WMvx5gLR4g69Bu4gs...
apple-domain-verification=s7lypSmtIRNEf43n
asv=c7519f930ae5823a397f54de28c3f60b
brevo-code:cfa92b6a811325c57a586de9b893f676
adobe-idp-site-verification=1ab6cb17-3551-4869-9296-fb097a240ce6
jamf-site-verification=kqKOZmPM_pRLVx6hlcqSMg
sending_domain555812=3304d8eab997a478be9ab3f09a33a20e1905b4b3abef16f69a6bf82f090...
smartsheet-site-validation=8Ncxe6hlB8-aDOBDBp64Lu46AmXKXmvX
d365mktkey=0b9d6i6xF2m320TUtQiIzUYSNpW3Gj2ybCP12kiTsWwx
brevo-code:1a1686b8b2045fd87b379b3495066b91
CAALookup not available with standard resolver
Resolved in 676 ms

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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

A+
Crawlability
robots.txt present, sitemap with 19 URLs
PASS
robots.txt present, sitemap with 19 URLs
Info::
robots.txt is present
Got: 309 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 19 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 309 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Allow: /

# Disallow crawling of sensitive files and directories
# Disallow: /admin/
Disallow: /prerendered/

# Allow crawling of sitemap.xml file (optional)
Allow: /sitemap.xml

# Specify crawl rate limits (optional)
Crawl-Delay: 10

# Sitemap location
Sitemap: https://www.uga.edu/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 19 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
uga.edu — 38 years, 7 months old, hosted on AWS
PASS
uga.edu — 38 years, 7 months old, hosted on AWS
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: AWS
Got: AS16509
Domain expiry

15 days

July 31, 2026

SSL certificate

211 days

Issued by Amazon

Domain age

38 years, 7 months

Registered March 14, 1988

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

15.197.234.180

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 14, 1988 (38 years, 7 months ago)
Expires July 31, 2026 (3 months)
Last Updated June 4, 2025
Name Servers dns2.uga.edu, dns4.uga.edu, dns3.uga.edu
Registrant University of Georgia
Hosting
IP Address 15.197.234.180
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (1.0s)
A
HTTP Probe Timing
Total 483 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
232 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.
167 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
483 ms
Total Time Total request time from DNS lookup through full response.
483 ms

Connection waterfall

DNS Lookup 232 ms TCP Connect 1 ms TLS Handshake 167 ms Server Processing 83 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