Skip to content
https://unm.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
73
GRADE
C
FIX
3
REVIEW
3
PASS
3
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
3 PASS 3 REVIEW 3 FIX
D
Redirect Chain
Action
2 redirect(s), 3276 ms total
FIX
2 redirect(s), 3276 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://unm.edu to https://www.unm.edu/
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: http://www.unm.edu/
Warning::
Redirect overhead: 3276 ms total
Got: 3276 ms

https://unm.edu

1133 ms · HTTP/1.1

301

http://www.unm.edu/

803 ms · HTTP/1.0

302

https://www.unm.edu/

1340 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unm.edu3011133 msHTTP/1.1
2http://www.unm.edu/302803 msHTTP/1.0BigIP
3https://www.unm.edu/2001340 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://unm.edu to https://www.unm.edu/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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

D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
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
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

200https://www.unm.edu/
200https://unm.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://unm.edu/ → http://www.unm.edu/

HTTP version does not redirect to HTTPS

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
HTTP Probe Timing
Total 1232 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
146 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
227 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
650 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.23 s
Total Time Total request time from DNS lookup through full response.
1.23 s

Connection waterfall

DNS Lookup 146 ms TCP Connect 227 ms TLS Handshake 650 ms Server Processing 210 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
95 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

95
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, 796 ms lookup
PASS
1 A records, 796 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 129.24.172.124
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: pdnsbox.id.nmt.edu, externaldns0.nmt.edu, ns1.unm.edu, ns2.unm.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 (796 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 796 ms
A129.24.172.124
AAAA—
CNAME—
NSpdnsbox.id.nmt.edu, externaldns0.nmt.edu, ns1.unm.edu, ns2.unm.edu
MX
5 unm-edu.mail.protection.outlook.com
TXT
d365mktkey=7ffx77jzky72hf0xhqzpdnzal
d365mktkey=14mt5liikiawj58jkfnm6eoo4
SPF v=spf1 include:spf.protection.outlook.com include:spf-ext.unm.edu exists:%{i}._s...
anthropic-domain-verification-s81p6x=GtDjreA5cdQVRU5twqVt05q6B
apple-domain-verification=i21Rmnp3kMxjyOsL
smartsheet-site-validation=UCKJGPomcSkOEEuysWTz2x2umXtv9j-Z
qjqk6tdrkmopfp5m2j33pkmo2c
sending_domain847783=d935300f6547adde7e4295af38a181e15529b8eb9a58a7d757ea51cbba0...
MS=ms33713651
E7kcO4Z9/K4NFtBXeTmVR84db1ExlBhc0up4udLENHBgVlLbyd5io04z9+KWfdS5OnPEtHRB5zp01VMR...
bw=/LNkne90tgaC/vlJhmsVBACgGoI5Rv1PkTpU4e3nLw/p
google-site-verification=-MjQXj6AZH8Vta03ajXcDJ-xE8sGuN7Ig2RA4no8te8
cisco-ci-domain-verification=621b8cc06dad3498315083d9c2aae818f5948147d454465d74c...
adobe-idp-site-verification=ae2c06b3-e720-41e1-a11b-efe29c6da3e6
google-gws-recovery-domain-verification=53756480
vmware-cloud-verification-4c0366e9-cee9-40da-95e2-5e3c72bcae1f
adobe-sign-verification=695d118630e71cd45502c7578c1b66da
google-site-verification=7iwR8dxmarTPWxgg65DO5qo-lNqkARUiy1RECbMoLGc
atlassian-domain-verification=yIhOQk6VPZdTEKp02VQJ3SqSDJqnRZBJPPTpm38piDS8lcUtw3...
ecostruxure-it-verification=d51743f8-79b4-4d01-9810-c0d99693a777
infoblox-domain-mastery=54db02c30ad89abb1341a4a820d90a4ce97881fbee931c3f68915de7...
google-site-verification=suDeBu3cQ5JEfYn92UdyZqkDPVCRI3QFK4dbV1tzUNk
CAALookup not available with standard resolver
Resolved in 796 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 123 URLs
PASS
robots.txt present, sitemap with 123 URLs
Info::
robots.txt is present
Got: 99 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 123 entries
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 99 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# robots.txt

User-agent: *

Disallow: 

Disallow: /cgi-bin/

Disallow: /tmp/

Disallow: /includes/
sitemap.xml 200 OK
Type URL Set URLs 123 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
unm.edu — 40 years, 2 months old, hosted on UNM-AS - University of New Mexico, US
PASS
unm.edu — 40 years, 2 months old, hosted on UNM-AS - University of New Mexico, US
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: UNM-AS - University of New Mexico, US
Got: AS3388
Domain expiry

19 days

July 31, 2026

SSL certificate

95 days

Issued by Internet2

Domain age

40 years, 2 months

Registered August 27, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UNM-AS - University of New Mexico, US

ASN AS3388

129.24.172.124

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 August 27, 1986 (40 years, 2 months ago)
Expires July 31, 2026 (3 months)
Last Updated July 11, 2023
Name Servers ns1.unm.edu, ns2.unm.edu
Registrant University of New Mexico
Hosting
IP Address 129.24.172.124
ASN AS3388 (UNM-AS - University of New Mexico, US)
Provider UNM-AS - University of New Mexico, 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