Skip to content
https://auburn.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
5
PASS
3
INFO
0
Probed from Madrid, Spain
200 OK
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.

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, sitemap with 1 URLs
REVIEW
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 115 bytes
Info::
sitemap.xml is present
Warning::
sitemap.xml contains invalid XML
Search engines may not be able to parse the sitemap. Fix XML validation errors.
Info::
sitemap.xml contains 1 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

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 115 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /student_info/omega_phi_alpha/images/members
Disallow: /academic/rotc/afrotc/CurrentCadets/
sitemap.xml 200 OK
Type URL Set URLs 1 entries Valid XML No
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.auburn.edu/
200https://auburn.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://auburn.edu/ https://auburn.edu/

Use 301 (permanent) instead of 302 (temporary)

B
HTTP Probe Timing
Total 880 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
133 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
109 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
221 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
881 ms
Total Time Total request time from DNS lookup through full response.
881 ms

Connection waterfall

DNS Lookup 133 ms TCP Connect 109 ms TLS Handshake 221 ms Server Processing 418 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
189 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

189
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, 872 ms lookup
PASS
1 A records, 872 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 131.204.138.170
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: asnsvr.asc.edu, dns.eng.auburn.edu, dns.auburn.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 (872 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 872 ms
A131.204.138.170
AAAA
CNAME
NSasnsvr.asc.edu, dns.eng.auburn.edu, dns.auburn.edu
MX
10 auburn-edu.mail.protection.outlook.com
TXT
google-site-verification=OcdCBhxVeEgkZ5_19KT4s6g7HFjgoxYeT9DNeyugwzE
wpe-verification=v3mg5
detectify-verification=905d8e6df6d0b54248c2296fe4898a86
google-site-verification=SmE6QR9ECK1Wy6_kQZYzfv9mUmDYbndcKquFIBsXb2M
sending_domain164641=c2c849a73e57fcfc81ed8fe3efaccee815fcc64b873c8b1f87c661eb9d9...
nintex.5aea1cbdbff50f6d7df852b5
e2ma-verification=321fb
ZOOM_verify_Rz58dHSpZtPXbBM05QvJ1O
google-site-verification=zLfpIaMO5fLPvTOY7_5NHPBsN25pDO8YvvZaIWnwlRo
contractworksverify=K7qXpZWTJYLoN3Cb9aMV
onetrust-domain-verification=4fa5a3e8eb2b4d8d8bfee680f34c8a61
rhino_accounts=ff9401069cd5dca516578f6fc93e6642
google-site-verification=6cW0Zcu7XP6ZWqioO1UZjM2Nh-F-Gh3SJXCh2lR6Tbs
adobe-idp-site-verification=913b9d59-cc5b-4588-8f7b-5b3ec589d1c3
ZPV0S3EARF6MYAYK6LDYAHM9DCUTE63EREPBQ0EXO
docusign=3b414259-8407-4655-a9c7-7d505ddd1c97
nintex.62472803c8cf150069a83182
SFMC-qjblPKON0ZZ4AGwZHuq_6ZDEDeiJsX4BdF3N9kGJ
google-site-verification=Q6A-7Cl6rXxKkc5ReRnmPTPnyw3nDnNznC0fc8OaNu4
00D4P000001d6iP=1TBUg00000002hl
00DHo0000018QLa=1TBUo00000001P7
wpe-verification=cfwe
fwDCqCWG3sOX9UwNE0Nuij6gsGw79Q9a2HNhcaJT7y0EJ/afzZnE3FIzR54UAZ4dnj8MNufna+H6ePGT...
ms-domain-verification=784ec703-4b61-4025-9936-462b4eacc035
atlassian-domain-verification=IjmDOt88djnLjEvhWX2Qkc4OKk4RuxRNv/p8TPwErDdZI00Ipp...
docusign=42911627-a26c-405e-97de-4db5ee56a718
apple-domain-verification=ui3lcIvLCKGZc8zT
asv=904de25cc7790e2f05b6f9a829d76e22
SPF v=spf1 ip4:131.204.0.0/16 ip4:23.253.182.0/23 ip4:23.253.213.70 ip4:72.10.184.10...
00DVG000006hcQE=1TBVG0000000FlR
CAALookup not available with standard resolver
Resolved in 872 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://auburn.edu

https://auburn.edu

746 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://auburn.edu200746 msHTTP/1.1Apache/2.4.62 (Red Hat Enterprise Linux)
A+
Domain Intelligence
auburn.edu — 38 years, 5 months old, hosted on AUBURN - Auburn University, US
PASS
auburn.edu — 38 years, 5 months old, hosted on AUBURN - Auburn University, US
Info::
Domain registered until Jul 31, 2028 (2 years, 3 months remaining)
Info::
Hosting: AUBURN - Auburn University, US
Got: AS6112
Domain expiry

776 days

July 31, 2028

SSL certificate

189 days

Issued by Internet2

Domain age

38 years, 5 months

Registered May 12, 1988

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AUBURN - Auburn University, US

ASN AS6112

131.204.138.170

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created May 12, 1988 (38 years, 5 months ago)
Expires July 31, 2028 (2 years, 3 months)
Last Updated August 11, 2025
Name Servers dns.eng.auburn.edu, asnsvr.asc.edu, dns.auburn.edu
Registrant Auburn University
Hosting
IP Address 131.204.138.170
ASN AS6112 (AUBURN - Auburn University, US)
Provider AUBURN - Auburn University, US
Data source: whois (1.0s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback