Skip to content
https://ttu.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
88
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more ▾

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

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

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

300
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, 56 ms lookup
PASS
1 A records, 56 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 129.118.58.15
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: ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info, ns1-05.azure-dns.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: 56 ms
Got: 56 ms
A129.118.58.15
AAAA—
CNAME—
NSns2-05.azure-dns.net, ns3-05.azure-dns.org, ns4-05.azure-dns.info, ns1-05.azure-dns.com
MX
0 ttu-edu.mail.protection.outlook.com
TXT
lIYN5xenqPSHSY+lFvuiAE3AStAfhgkLa/8JKvnSSVRmFqO8prkkKCgrWla32m71wOHRU66K97xNKNMb...
MS=ms30197301
adobe-idp-site-verification=ff073f90c4da80c0ee92d3db1ba32bd333c6f3a341663d58d3d9...
SPF v=spf1 redirect=9dd2hzwe._spf._d.mim.ec
fpqydlkv9wlc95nfjbh1py67wdly0q83
atlassian-domain-verification=o1n0Izzs9DnNdLdIaaBwaqGbaaZwTToEtJzzJx3ah0n/LyZCez...
pardot582863=5cca27502386ae37e7f8e77362e574c3ea47294dbaf7825c88616213a741fab4
atlassian-sending-domain-verification=611bdab0-10c3-4474-a266-7b7de1d06fc8
CAALookup not available with standard resolver
Resolved in 56 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+
Redirect Chain
0 redirect(s), 578 ms total
PASS
0 redirect(s), 578 ms total
Info::
Redirect overhead: 578 ms total
Got: 578 ms

https://ttu.edu

578 ms · HTTP/1.0 FINAL

#URLStatusTimeProtocolServer
1https://ttu.edu301578 msHTTP/1.0BigIP
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

https://www.ttu.edu/
200https://ttu.edu/

HTTP → HTTPS

301http://ttu.edu/ → https://www.ttu.edu/

Consistent

A+
Domain Intelligence
ttu.edu — 38 years, 1 months old, hosted on TTUNET - Texas Tech University, US
PASS
ttu.edu — 38 years, 1 months old, hosted on TTUNET - Texas Tech University, US
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: TTUNET - Texas Tech University, US
Got: AS10421
Domain expiry

47 days

July 31, 2026

SSL certificate

300 days

Issued by Internet2

Domain age

38 years, 1 months

Registered September 16, 1988

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

TTUNET - Texas Tech University, US

ASN AS10421

129.118.58.15

Registrar

Registrar unknown

Lock status unknown 4 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 September 16, 1988 (38 years, 1 months ago)
Expires July 31, 2026 (3 months)
Last Updated February 20, 2026
Name Servers ns2-05.azure-dns.net, ns3-05.azure-dns.org, ns1-05.azure-dns.com, ns4-05.azure-dns.info
Registrant Texas Tech University
Hosting
IP Address 129.118.58.15
ASN AS10421 (TTUNET - Texas Tech University, US)
Provider TTUNET - Texas Tech University, US
Data source: whois (1.0s)
A
HTTP Probe Timing
Total 729 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
51 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
166 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
343 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
729 ms
Total Time Total request time from DNS lookup through full response.
729 ms

Connection waterfall

DNS Lookup 51 ms TCP Connect 166 ms TLS Handshake 343 ms Server Processing 169 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