Skip to content
https://nmsu.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
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
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
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.nmsu.edu/
200https://nmsu.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://nmsu.edu/ → https://nmsu.edu/

Consistent

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

Connection waterfall

DNS Lookup 169 ms TCP Connect 25 ms TLS Handshake 64 ms Server Processing 593 ms Content Transfer 25 ms
B
TLS Certificate Expiry & Recommendations
101 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

101
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, 177 ms lookup
PASS
1 A records, 177 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 216.21.13.176
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: dns2.nmsu.edu, dns1.nmsu.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
Info::
DNS resolution time: 177 ms
Got: 177 ms
A216.21.13.176
AAAA—
CNAME—
NSdns2.nmsu.edu, dns1.nmsu.edu
MX
10 nmsu-edu.mail.protection.outlook.com
TXT
SPF v=spf1 ip4:128.123.0.0/16 ip4:192.88.140.88/29 ip4:74.87.165.32/27 ip4:173.224.6...
adobe-idp-site-verification=e2deda5e05f2a392d4a3954a84aa6802b26664031fce63660d7e...
F1KNPAS3PQ96F8KJ5NUIYE1QJEWDOV47M80J167F3
jamf-site-verification=_2-dkCIFfYtAr1e5jpVrPw
autodesk-domain-verification=1o8_XAZo_DMod44OnXMu
CAALookup not available with standard resolver
Resolved in 177 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://nmsu.edu

https://nmsu.edu

591 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://nmsu.edu200591 msHTTP/1.1Apache
A+
Domain Intelligence
nmsu.edu — 39 years, 5 months old, hosted on TUT-AS - Total Uptime Technologies, LLC, US
PASS
nmsu.edu — 39 years, 5 months old, hosted on TUT-AS - Total Uptime Technologies, LLC, US
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: TUT-AS - Total Uptime Technologies, LLC, US
Got: AS53334
Domain expiry

45 days

July 31, 2026

SSL certificate

101 days

Issued by Internet2

Domain age

39 years, 5 months

Registered May 27, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

TUT-AS - Total Uptime Technologies, LLC, US

ASN AS53334

216.21.13.176

Registrar

Registrar unknown

Lock status unknown 2 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 May 27, 1987 (39 years, 5 months ago)
Expires July 31, 2026 (3 months)
Last Updated July 7, 2025
Name Servers dns1.nmsu.edu, dns2.nmsu.edu
Registrant New Mexico State University
Hosting
IP Address 216.21.13.176
ASN AS53334 (TUT-AS - Total Uptime Technologies, LLC, US)
Provider TUT-AS - Total Uptime Technologies, LLC, US
Data source: whois (1.2s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback