Skip to content
https://uvm.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 Sao Paulo, Brazil
302 Found
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), 1109 ms total
REVIEW
1 redirect(s), 1109 ms total
Info::
Single redirect
Got: https://uvm.edu → https://www.uvm.edu/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://uvm.edu
Warning::
Redirect overhead: 1109 ms total
Got: 1109 ms

https://uvm.edu

493 ms · HTTP/1.1

302

https://www.uvm.edu/

617 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uvm.edu302493 msHTTP/1.1nginx/1.29.8
2https://www.uvm.edu/200617 msHTTP/1.1nginx/1.29.8

See the visual redirect chain in the HTTP Probe tab →

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

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

C
URL Variants
Action
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
Warning::
HTTP→HTTPS redirect uses 302 instead of 301
Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.uvm.edu/
200https://uvm.edu/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://uvm.edu/ https://www.uvm.edu/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

311
days left
0d 30d 60d 90d+

Recommended actions

  • 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, 134 ms lookup
PASS
1 A records, 134 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 132.198.101.197
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: ns1.uvm.edu, ns2.uvm.edu
Info::
4 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: 134 ms
Got: 134 ms
A132.198.101.197
AAAA
CNAME
NSns1.uvm.edu, ns2.uvm.edu
MX
5 sandpiper.in-mail.uvm.edu
5 shoveler.in-mail.uvm.edu
5 plover.in-mail.uvm.edu
5 wigeon.in-mail.uvm.edu
TXT
ZOOM_verify_AHlRX4EyRG6nUbH7liKnFw
SPF v=spf1 mx ip4:132.198.0.0/16 ip6:2620:104:E000::/40 ~all
d1b714f78b30078904228881a683e5
wrike-verification=NjQwMTI4MzpiMDZhNmFkN2JlMGE5YWI3ZTc5OTZkOTc2MjY1MThhNDY3OThmZ...
google-site-verification=fpAcS39Lb2RlUTO7juCm-P95FmMx8xoqNeDoWKOlu9g
cisco-ci-domain-verification=401728b3a13c45869fe9be0bf75f3aea9d7e277743a9f4b95e6...
autodesk-domain-verification=BL7s6eZeY5HQFaVXycnU
smartsheet-site-validation=_xcYth-7A54pxZL0u-uk5x1Cb37C9DDr
apple-domain-verification=nhesw5inOqwecMno
Uk/uOah7Bm2J2rnFHIrbJvXTw2VgWlyndyRtHCIgVAhXo4RnpTTlkINVAaGteCIDA0TtfnZ2NIyEWW4d...
reftab-domain-verification=4a4a9484806e8254d08d25fa6a2d57dc
CAALookup not available with standard resolver
Resolved in 134 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+
Crawlability
robots.txt present, sitemap with 5 URLs
PASS
robots.txt present, sitemap with 5 URLs
Info::
robots.txt is present
Got: 2047 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 5 entries
Info::
Sitemap index with 5 child sitemaps
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 2047 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
Allow: /sitemap.xml
# 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

A+
Domain Intelligence
uvm.edu — 39 years, 7 months old, hosted on UVM-EDU-AS - University of Vermont, US
PASS
uvm.edu — 39 years, 7 months old, hosted on UVM-EDU-AS - University of Vermont, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: UVM-EDU-AS - University of Vermont, US
Got: AS1351
Domain expiry

377 days

July 31, 2027

SSL certificate

311 days

Issued by Internet2

Domain age

39 years, 7 months

Registered April 14, 1987

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UVM-EDU-AS - University of Vermont, US

ASN AS1351

132.198.101.197

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created April 14, 1987 (39 years, 7 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated July 26, 2024
Name Servers ns1.uvm.edu, ns2.uvm.edu
Registrant University of Vermont
Hosting
IP Address 132.198.101.197
ASN AS1351 (UVM-EDU-AS - University of Vermont, US)
Provider UVM-EDU-AS - University of Vermont, US
Data source: whois (1.2s)
A
HTTP Probe Timing
Total 506 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
140 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
119 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
127 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
506 ms
Total Time Total request time from DNS lookup through full response.
506 ms

Connection waterfall

DNS Lookup 140 ms TCP Connect 119 ms TLS Handshake 127 ms Server Processing 119 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