Skip to content
https://unr.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
4
PASS
4
INFO
0
Probed from Madrid, Spain
200 OK
Checks
9
4 PASS 4 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.

B
DNS Records
1 A records, 199 ms lookup
REVIEW
1 A records, 199 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 134.197.15.101
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: cmsdss-tip.unr.edu
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 199 ms
Got: 199 ms
A134.197.15.101
AAAA—
CNAMEcmsdss-tip.unr.edu
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 199 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

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

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

Connection waterfall

DNS Lookup 503 ms TCP Connect 158 ms TLS Handshake 318 ms Server Processing 231 ms Content Transfer 22 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

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.unr.edu

https://www.unr.edu

725 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.unr.edu200725 msHTTP/1.1Microsoft-IIS/10.0
A+
Crawlability
robots.txt present, sitemap with 19077 URLs
PASS
robots.txt present, sitemap with 19077 URLs
Info::
robots.txt is present
Got: 25 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 19077 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 25 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-Agent: *

Disallow:
sitemap.xml 200 OK
Type URL Set URLs 19077 entries Valid XML Yes
Sample URLs:
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

200https://www.unr.edu/
https://unr.edu/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
unr.edu — 39 years, 11 months old, hosted on NSHE-NEVADANET - Nevada System of Higher Education, US
PASS
unr.edu — 39 years, 11 months old, hosted on NSHE-NEVADANET - Nevada System of Higher Education, US
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: NSHE-NEVADANET - Nevada System of Higher Education, US
Got: AS3851
Domain expiry

45 days

July 31, 2026

SSL certificate

189 days

Issued by Internet2

Domain age

39 years, 11 months

Registered December 11, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

NSHE-NEVADANET - Nevada System of Higher Education, US

ASN AS3851

134.197.15.101

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 11, 1986 (39 years, 11 months ago)
Expires July 31, 2026 (3 months)
Last Updated March 17, 2026
Name Servers nsx3.unr.edu, nsx1.unr.edu, nsx2.unr.edu
Registrant University of Nevada, Reno
Hosting
IP Address 134.197.15.101
ASN AS3851 (NSHE-NEVADANET - Nevada System of Higher Education, US)
Provider NSHE-NEVADANET - Nevada System of Higher Education, US
Data source: whois (1.1s)
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback