Skip to content
https://unl.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
75
GRADE
C
FIX
2
REVIEW
4
PASS
3
INFO
0
Probed from Madrid, Spain
302 Found
Checks
9
3 PASS 4 REVIEW 2 FIX
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 302 Expected: 301 redirect to HTTPS

www / non-www

200https://www.unl.edu/
200https://unl.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://unl.edu/ → http://www.unl.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.

B
Redirect Chain
1 redirect(s), 1129 ms total
REVIEW
1 redirect(s), 1129 ms total
Info::
Single redirect
Got: https://unl.edu → https://www.unl.edu/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1129 ms total
Got: 1129 ms

https://unl.edu

537 ms · HTTP/1.1

301

https://www.unl.edu/

591 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unl.edu301537 msHTTP/1.1Microsoft-IIS/10.0
2https://www.unl.edu/200591 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 2027 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 2027 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
#
# robots.txt
#
# This file is to prevent the crawling and indexing of certain parts
# of your site by web crawlers and spiders run by sites like Yahoo!
# and Google. By telling these "robots" where not to go on your site,
# you save bandwidth and server resources.
#
# This file will be ignored unless it is at the root of your host:
# Used:    http://example.com/robots.txt
# Ignored: http://example.com/site/robots.txt
#
# For more information about the robots.txt standard, see:
# http://www.robotstxt.org/robotstxt.html

User-agent: *
# CSS, JS, Images
Allow: /core/*.css$
Allow: /core/*.css?
Allow: /core/*.js$
Allow: /core/*.js?
Allow: /core/*.gif
Allow: /core/*.jpg
Allow: /core/*.jpeg
Allow: /core/*.png
Allow: /core/*.svg
Allow: /profiles/*.css$
Allow: /profiles/*.css?
Allow: /profiles/*.js$
Allow: /profiles/*.js?
Allow: /profiles/*.gif
Allow: /profiles/*.jpg
Allow: /profiles/*.jpeg
Allow: /profiles/*.png
Allow: /profiles/*.svg
# Directories
Disallow: /core/
Disallow: /profiles/
# Files
Disallow: /README.md
Disallow: /composer/Metapackage/README.txt
Disallow: /composer/Plugin/ProjectMessage/README.md
Disallow: /composer/Plugin/Scaffold/README.md
Disallow: /composer/Plugin/VendorHardening/README.txt
Disallow: /composer/Template/README.txt
Disallow: /modules/README.txt
Disallow: /sites/README.txt
Disallow: /themes/README.txt
Disallow: /web.config
# Paths (clean URLs)
Disallow: /admin/
Disallow: /comment/reply/
Disallow: /filter/tips
Disallow: /node/add/
Disallow: /search/
Disallow: /user/register
Disallow: /user/password
Disallow: /user/login
Disallow: /user/logout
Disallow: /media/oembed
Disallow: /*/media/oembed
# Paths (no clean URLs)
Disallow: /index.php/admin/
Disallow: /index.php/comment/reply/
Disallow: /index.php/filter/tips
Disallow: /index.php/node/add/
Disallow: /index.php/search/
Disallow: /index.php/user/password
Disallow: /index.php/user/register
Disallow: /index.php/user/login
Disallow: /index.php/user/logout
Disallow: /index.php/media/oembed
Disallow: /index.php/*/media/oembed
sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

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

Certificate validity

162
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
4 A records, 620 ms lookup
PASS
4 A records, 620 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 129.93.168.40, 129.93.168.41, 129.93.168.43, 129.93.168.42
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-110.awsdns-13.com, ns-1531.awsdns-63.org, ns-1812.awsdns-34.co.uk, ns-724.awsdns-26.net
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 (620 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 620 ms
A129.93.168.40, 129.93.168.41, 129.93.168.43, 129.93.168.42
AAAA—
CNAME—
NSns-110.awsdns-13.com, ns-1531.awsdns-63.org, ns-1812.awsdns-34.co.uk, ns-724.awsdns-26.net
MX
10 mxa-00246402.gslb.pphosted.com
10 mxb-00246402.gslb.pphosted.com
TXT
ZOOM_verify_CTC0oZ0bTCiDnu6vpTvEyA
Dynatrace-site-verification=e5bcc694-cf1e-4c7a-8783-1c2ffaa4cfbf__v6j3bae1ad59ef...
docusign=a86f4753-9624-4588-8dd1-269aefc00208
atlassian-domain-verification=F7sE6lILWyEFMLayqtLtYEMS8X8zMxMVvkDA18IeJb9YFf7OJR...
apple-domain-verification=TzFPo0RgKGfmtbig
box-domain-verification=0b36362ce455b2f6194034a2e304b887d9da3b491bc376559fa561d6...
adobe-idp-site-verification=d557a4d1-1f2d-407e-85f0-eedbbe5dd662
facebook-domain-verification=azwy7ny6hjnji55ubgn2vl1chydkkx
MS=ms12464472
PnK5haOQj/A/5RTOlbfOVphM7WWSaXu3cr2+D8C28Vo=
e2ma-verification=n9c
openai-domain-verification=dv-l4o1dAuFPKyrRb0JYG5f0vH0
airtable-verification=ae79136089181a5402a7952973228f89
docusign=349e6f39-8de3-47c8-b69b-9e353d495cbc
status-page-domain-verification=3ysb9t5m7y6j
v=DKIM1; h=sha256; k=rsa; s=email; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQE...
MS=ms61243123
_globalsign-domain-verification=LBGN_PGPzs-K_ugvlmQc5pBRof3QCVximyhc9hNKsU
SPF v=spf1 include:spf1.unl.edu include:spf2.unl.edu include:spf3.unl.edu include:sp...
google-site-verification=zTHeeWJgyLp76HnvlTbd6xltqXQpKChoufH19VaDNWc
CAALookup not available with standard resolver
Resolved in 620 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+
Domain Intelligence
unl.edu — 39 years, 3 months old, hosted on NU-AS - The Board of Regents of the University of Nebraska, US
PASS
unl.edu — 39 years, 3 months old, hosted on NU-AS - The Board of Regents of the University of Nebraska, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: NU-AS - The Board of Regents of the University of Nebraska, US
Got: AS7896
Domain expiry

380 days

July 31, 2027

SSL certificate

162 days

Issued by Internet2

Domain age

39 years, 3 months

Registered July 28, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

NU-AS - The Board of Regents of the University of Nebraska, US

ASN AS7896

129.93.168.41

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created July 28, 1987 (39 years, 3 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated June 4, 2024
Name Servers ns-1531.awsdns-63.org, ns-110.awsdns-13.com, ns-1812.awsdns-34.co.uk, ns-724.awsdns-26.net
Registrant University of Nebraska - Lincoln
Hosting
IP Address 129.93.168.41
ASN AS7896 (NU-AS - The Board of Regents of the University of Nebraska, US)
Provider NU-AS - The Board of Regents of the University of Nebraska, US
Data source: whois (0.9s)
A
HTTP Probe Timing
Total 559 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
27 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
130 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
271 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
560 ms
Total Time Total request time from DNS lookup through full response.
560 ms

Connection waterfall

DNS Lookup 27 ms TCP Connect 130 ms TLS Handshake 271 ms Server Processing 131 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