Skip to content
https://gsu.edu

Infrastructure

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

https://gsu.edu

375 ms · HTTP/1.1

302

https://www.gsu.edu/

865 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://gsu.edu302375 msHTTP/1.1Apache/2.4.41 (Ubuntu)
2https://www.gsu.edu/200865 msHTTP/1.1cloudflare

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

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.gsu.edu/
200https://gsu.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

348
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
1 A records, 640 ms lookup
PASS
1 A records, 640 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 104.239.136.235
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
6 nameserver(s) configured
Got: ns1.usg.edu, ns3.usg.edu, ns2.usg.edu, dns-ext2.gsu.edu, ns4.usg.edu, dns-ext1.gsu.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 (640 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 640 ms
A104.239.136.235
AAAA
CNAME
NSns1.usg.edu, ns3.usg.edu, ns2.usg.edu, dns-ext2.gsu.edu, ns4.usg.edu, dns-ext1.gsu.edu
MX
0 gsu-edu.mail.protection.outlook.com
TXT
webexdomainverification.4C675B8BA984B136E053AB06FC0A3F65=7c65b3e8-fcaf-43ee-814d...
ciscocidomainverification=581df163e549b4dd0af62da736f22f71d57c7465f65326947f17fa...
airtable-verification=ad852c88ee36576a632db7137ed8fffe
d365mktkey=yvv72jNHFQxWycEXMxgN256ZcfQ8Ta2pZMfxE8H6A7Ex
status-page-domain-verification=m3rrrd4cykwp
adobe-sign-verification=e7c1b471b1f28f251ec0776519d31f6
pardot1063302=a19847b311594f77ef9f1b694eff2c9271894a13c97bfc11d492a0292ae52f7c
airtable-verification=efeaf8833477d2d9879bdd94baeefb2c
adobe-idp-site-verification=42a7a470-0872-4bc3-9dca-3bd86be2b827
extensis-domain-verification=69f52821-6dc8-42ab-bed4-4395d81672d8
smartsheet-site-validation=hgGKpzO7QaB4nKY76xMjMpykc3WDvVXO
atlassian-domain-verification=VVbSS/Y2WMZfMxihvmT2ZWmpKKl0aL5DWjuhvtJ9iHl6ZRH84T...
amazonses:HB55EuACTyzG7s5+kLC/m1WtLeWL8a1JzmiC+BgQWUQ=
sophos-domain-verification=d6c16885c358ba6d3ee6126c402dda4338e9df5ac54bfc7b12abc...
SPF v=spf1 ip4:131.96.2.42 ip4:131.96.2.41 include:spfb.gsu.edu a:c.spf.service-now....
d365mktkey=mqUdtEp5EcWewOjB1eNFtBNx0AKDQxnrpYX2DAwv2MYx
sending_domain1063302=78e8cb8b01e2acd81fb8e5f6b1d708d682c9e3f041963dc4197f8c550a...
apple-domain-verification=zoLqJCVLKqC7TQMN
amazonses:rCkC5i8vgdVpE+wG8IaPyOv80oDn2yk58U3Pp9pqQMU=
facebook-domain-verification=7469k9durhf0gpvqh5f3589pau5cwa
dell-technologies-domain-verification=gsu.edu_ad9a35e4-563a-4f5d-9038-6b32008d66...
ZOOM_verify_zVdgrBt5eeVm44BLbwitaG
ZOOM_verify_0ceLYS5ZAMdZHYawEPctdg
canva-site-verification=kGZHfH2WfmkP6KayA9DobA
CAALookup not available with standard resolver
Resolved in 640 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.

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 49 URLs
PASS
robots.txt present, sitemap with 49 URLs
Info::
robots.txt is present
Got: 2175 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 49 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 2175 B Sitemaps referenced 1 User-agents Applebot-Extended, Bytespider, CCBot, ClaudeBot, CloudflareBrowserRenderingCrawler, GPTBot, Google-Extended, meta-externalagent, *, Amazonbot Blocking No — crawling allowed
# As a condition of accessing this website, you agree to abide by the following
# content signals:

# (a)  If a Content-Signal = yes, you may collect content for the corresponding
#      use.
# (b)  If a Content-Signal = no, you may not collect content for the
#      corresponding use.
# (c)  If the website operator does not include a Content-Signal for a
#      corresponding use, the website operator neither grants nor restricts
#      permission via Content-Signal with respect to the corresponding use.

# The content signals and their meanings are:

# search:   building a search index and providing search results (e.g., returning
#           hyperlinks and short excerpts from your website's contents). Search does not
#           include providing AI-generated search summaries.
# ai-input: inputting content into one or more AI models (e.g., retrieval
#           augmented generation, grounding, or other real-time taking of content for
#           generative AI search answers).
# ai-train: training or fine-tuning AI models.

# ANY RESTRICTIONS EXPRESSED VIA CONTENT SIGNALS ARE EXPRESS RESERVATIONS OF
# RIGHTS UNDER ARTICLE 4 OF THE EUROPEAN UNION DIRECTIVE 2019/790 ON COPYRIGHT
# AND RELATED RIGHTS IN THE DIGITAL SINGLE MARKET.

# BEGIN Cloudflare Managed content

User-agent: *
Content-Signal: search=yes,ai-train=no
Allow: /

User-agent: Amazonbot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: CloudflareBrowserRenderingCrawler
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: meta-externalagent
Disallow: /

# END Cloudflare Managed Content

User-agent: *
Sitemap: https://*.gsu.edu/sitemap_index.xml
Disallow: /wp-admin/
Disallow: /wp-includes/
Disallow: /calendar/action~posterboard/
Disallow: /calendar/action~agenda/
Disallow: /calendar/action~oneday/
Disallow: /calendar/action~month/
Disallow: /calendar/action~week/
Disallow: /calendar/action~stream/
Disallow: /*/action~*
Disallow: /*/month_offset~*
Disallow: /*/exact_date~*
Disallow: /*/cat_ids~*
Disallow: /*/tag_ids~*
A+
Domain Intelligence
gsu.edu — 36 years, 4 months old, hosted on Rackspace
PASS
gsu.edu — 36 years, 4 months old, hosted on Rackspace
Info::
Domain registered until Jul 31, 2028 (2 years, 3 months remaining)
Info::
Hosting: Rackspace
Got: AS33070
Domain expiry

778 days

July 31, 2028

SSL certificate

348 days

Issued by Internet2

Domain age

36 years, 4 months

Registered June 25, 1990

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Rackspace

ASN AS33070

104.239.136.235

Registrar

Registrar unknown

Lock status unknown 6 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created June 25, 1990 (36 years, 4 months ago)
Expires July 31, 2028 (2 years, 3 months)
Last Updated April 3, 2026
Name Servers ns3.usg.edu, ns2.usg.edu, dns-ext2.gsu.edu, dns-ext1.gsu.edu, ns4.usg.edu, ns1.usg.edu
Registrant Georgia State University
Hosting
IP Address 104.239.136.235
ASN AS33070 (RMH-14 - Rackspace Hosting, US)
Provider Rackspace
Data source: whois (0.9s)
A
HTTP Probe Timing
Total 490 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
118 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
123 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
127 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
490 ms
Total Time Total request time from DNS lookup through full response.
491 ms

Connection waterfall

DNS Lookup 118 ms TCP Connect 123 ms TLS Handshake 127 ms Server Processing 123 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