Skip to content
https://tamu.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Santa Clara, United States
301 Moved Permanently
Checks
9
5 PASS 3 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
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.tamu.edu/
200https://tamu.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://tamu.edu/ → https://www.tamu.edu:443/

Consistent

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

Certificate validity

266
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
2 A records, 10553 ms lookup
PASS
2 A records, 10553 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 75.2.123.204, 99.83.234.45
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ns1.tamu.edu, ns2.tamu.edu, ns3.tamu.edu
Info::
2 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 (10553 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 10553 ms
A75.2.123.204, 99.83.234.45
AAAA—
CNAME—
NSns1.tamu.edu, ns2.tamu.edu, ns3.tamu.edu
MX
10 tamu-relay.tamu.edu
100 smtp-relay.tamu.edu
TXT
ms=ms74999999
tamu.azurewebsites.net
e2ma-verification=4hccb
e2ma-verification=eyhbb
e2ma-verification=k45fb
e2ma-verification=pr1fb
e2ma-verification=sa6fb
e2ma-verification=ta6fb
e2ma-verification=un7fb
e2ma-verification=wl6fb
e2ma-verification=wtybb
e2ma-verification=zo1fb
mandrill_verify.h7er6raE5IiKhTEXjkM_CQ
docusign=7be6060a-425c-4689-bae9-25f5497bb483
docusign=9db61bfc-aa28-48e4-a727-e03a8ac79225
jamf-site-verification=8Vr2DObPXdvSL5-L8WvJdA
zoho-verification=zb95960090.zmverify.zoho.com
airtable-verification=237c5293eac75db5d9613ca0ad757aab
airtable-verification=26efa5dfc74071e1ae2133b732f8baa2
airtable-verification=7f9b76c535b86002ae3c7305518eabc9
airtable-verification=c246e76419d4d2ce05c793524f5ee632
amazonses:5Enu9IrxeDKi8/YmjFymoqDfCvcfMHx9vAgPHur1bDQ=
openai-domain-verification=dv-GRRdxrhcGwuMPv8xdumILtAO
smartsheet-site-validation=fPnaZcNcP6-o1OAunnOfSrxBT75EK8oF
perplexity-ai-domain-verification-yn637n=2fMsNzRT0FF2rA3wzJKr67kmC
google-site-verification=0yJOyuO9ISYcj-5AZGV_GouXcnY5iyKQy7RM501MJxM
google-site-verification=EZ_4EOX-DfqxHod6w4LxjeMhpxzqMF3dhO1hwY5Rc7A
google-site-verification=GBXS68BAiKd-p40xAQZxFUdvbMFGBXGfH7N-lSoQfH4
google-site-verification=gbLDbh-Q1KfBG2HlZvIUsuGLsaHEXnO_kW30uedj-nU
quickbase-site-verification-7decf3b1e1b28fbc23e2fd9e78861481457c332d
atlassian-sending-domain-verification=317ff8dd-0c54-4dbc-84d7-b8a3f5673baa
atlassian-sending-domain-verification=a9aa3b01-967b-4038-89b2-8e8a1357e04b
pardot455902=49d87e510c5f876c55ae3d0126992ab87f26dbe5c152558c870392c320218609
pardot895011=13f5b334120286511406da291145230ad13c6451a0d0d7d73952914260674bf0
FHikcf/HWK9SQK9BzqAFKtgbhKTtVF5ShZRTvIyN5OtiA6T3PHOmF4hgf549mDgKgm5B8ZREqAdfUURG...
sz5tnrqe22yljc95ectd7u3nauiwvkjnfjdp8ywsqypcghiutkk1hjmeum+rrmfczx7infnjusern2i2...
yuke0bcsl3x1xn6/2o6sgwvfu+4yt7zhpiozq725tz+dcy7jmxqfjzdsq6tom0rjfyborf1ypg0ks9gi...
adobe-idp-site-verification=4d354aa550e6abf768c5a39cde7b8e04ba9b8fb3697b28763eb3...
cisco-ci-domain-verification=723bd037562b7191c5429ce9ae1d72f3c6c627bc287f00ff7f2...
atlassian-domain-verification=9lGO5Gpkk8I6UlQhyksa2MfOqTSDtEH4TfMlShOboGL0xcaXzQ...
atlassian-domain-verification=SX81a26xZXI9jy8nyUrAmPa0DU2RKKr+7pXOgOHD3byqM1OTDm...
dell-technologies-domain-verification=tamu.edu_9f94503e-13af-41de-af8b-6b36c1c15...
SPF v=spf1 include:spf0.tamu.edu include:spf1.tamu.edu include:spf2.tamu.edu include...
CAALookup not available with standard resolver
Resolved in 10553 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
Redirect Chain
1 redirect(s), 390 ms total
PASS
1 redirect(s), 390 ms total
Info::
Single redirect
Got: https://tamu.edu → https://www.tamu.edu:443/ (301)
Info::
WWW normalization redirect

https://tamu.edu

305 ms · HTTP/1.1

301

https://www.tamu.edu:443/

84 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://tamu.edu301305 msHTTP/1.1awselb/2.0
2https://www.tamu.edu:443/20084 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

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

Disallow:


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

45 days

July 31, 2026

SSL certificate

266 days

Issued by Amazon

Domain age

38 years, 10 months

Registered December 14, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.123.204

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 December 14, 1987 (38 years, 10 months ago)
Expires July 31, 2026 (3 months)
Last Updated July 15, 2025
Name Servers ns3.tamu.edu, ns1.tamu.edu, ns2.tamu.edu
Registrant Texas A&M University
Hosting
IP Address 75.2.123.204
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: whois (0.5s)
A+
HTTP Probe Timing
Total 301 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
56 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
181 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
302 ms
Total Time Total request time from DNS lookup through full response.
302 ms

Connection waterfall

DNS Lookup 56 ms TCP Connect 3 ms TLS Handshake 181 ms Server Processing 62 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