Skip to content
https://unh.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
80
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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
Redirect Chain
1 redirect(s), 1017 ms total
REVIEW
1 redirect(s), 1017 ms total
Info::
Single redirect
Got: https://unh.edu → https://www.unh.edu/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1017 ms total
Got: 1017 ms

https://unh.edu

424 ms · HTTP/1.1

301

https://www.unh.edu/

593 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unh.edu301424 msHTTP/1.1nginx
2https://www.unh.edu/200593 msHTTP/1.1nginx

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
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.unh.edu/
200https://unh.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

121
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, 2274 ms lookup
PASS
1 A records, 2274 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 132.177.132.99
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: ns.usnh.edu, ns2.unh.edu, unhsst.unh.edu, nic.unh.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 (2274 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 2274 ms
A132.177.132.99
AAAA—
CNAME—
NSns.usnh.edu, ns2.unh.edu, unhsst.unh.edu, nic.unh.edu
MX
10 unh-edu.mail.protection.outlook.com
TXT
ecostruxure-it-verification=a5d461d6-381e-414f-a841-406d35adc6de
sending_domain1079943=ae1f99177527174f6fc6e3d92921ad8385ac4623d83562198ebb214dda...
MS=ms83123557
adobe-idp-site-verification=c72276468d8ad7daa06fc05b3fb7d859465513ffc061216675fe...
DZCT6MFEfQ
Sendinblue-code:160d1089769095a328703e634f5de06f
bCPyawUYSK6Mb3g4rkXkG8UamHfRF6oPVSuSN+Prgu9eqkpFCjbTD5/Iriv+oY/oiap0gYLVnvsknUbM...
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:sendersrv.com ~a...
brevo-code:2234ddef09ed2b8787c6d93f0d819572
brevo-code:59b3a18744d24f960bd78166f34f87c5
kalFjJr0aINP1W3NsIkMJ54W1nbfYaEq+KB2Sv59vuwk+IvYl3B6oS+BZXTUWWmV3sh8gOda8PKaPR06...
facebook-domain-verification=365v2rdn8vcv8khorj0t2omd96cjot
google-site-verification=EdWChc29r-pivLURIP1-SDQG5x_x7nn52SzSo_WaWUI
docusign=48670095-e238-4b1c-a4d8-46985245e60c
pardot1079943=a8105d204e2e4dd35693c1f35634df8109aafa853cbf62b4bbfdc6289e9c938c
p97pdo41uabdp794oeslgiqm0c
google-site-verification=uSIAdU9YfWQ1EKgirykwuhfTBnx8vYdX2saLBBehHkE
google-site-verification=RGZA0mMI8yyY4n5P5CCjwKkFispZEjJDQ0ZPM3n0ihs
CAALookup not available with standard resolver
Resolved in 2274 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 289 URLs
PASS
robots.txt present, sitemap with 289 URLs
Info::
robots.txt is present
Got: 2124 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 289 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 2124 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# Global UNH rules.
Disallow: /sites/default/files/*.pdf$

#
# 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

# Site specific robots.txt settings.
sitemap.xml 200 OK
Type URL Set URLs 289 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
unh.edu — 40 years old, hosted on USNH - University System of New Hampshire, US
PASS
unh.edu — 40 years old, hosted on USNH - University System of New Hampshire, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: USNH - University System of New Hampshire, US
Got: AS11745
Domain expiry

377 days

July 31, 2027

SSL certificate

121 days

Issued by Internet2

Domain age

40 years

Registered October 27, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

USNH - University System of New Hampshire, US

ASN AS11745

132.177.132.99

Registrar

Registrar unknown

Lock status unknown 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created October 27, 1986 (40 years ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated March 2, 2026
Name Servers unhsst.unh.edu, ns2.unh.edu, ns.usnh.edu, nic.unh.edu
Registrant University of New Hampshire
Hosting
IP Address 132.177.132.99
ASN AS11745 (USNH - University System of New Hampshire, US)
Provider USNH - University System of New Hampshire, US
Data source: whois (1.0s)
A
HTTP Probe Timing
Total 696 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
280 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
101 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
204 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
696 ms
Total Time Total request time from DNS lookup through full response.
696 ms

Connection waterfall

DNS Lookup 280 ms TCP Connect 101 ms TLS Handshake 204 ms Server Processing 112 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