Skip to content
https://ucar.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 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.

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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, 370 ms lookup
PASS
1 A records, 370 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.117.225.32
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: dnsx2.ucar.edu, dnsx1.ucar.edu, dnsnx2.nwsc.ucar.edu, dnsnx1.nwsc.ucar.edu, dns.ucar.edu
Info::
5 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 (370 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 370 ms
A128.117.225.32
AAAA—
CNAME—
NSdnsx2.ucar.edu, dnsx1.ucar.edu, dnsnx2.nwsc.ucar.edu, dnsnx1.nwsc.ucar.edu, dns.ucar.edu
MX
1 ASPMX.L.GOOGLE.COM
5 ALT2.ASPMX.L.GOOGLE.COM
5 ALT1.ASPMX.L.GOOGLE.COM
9 ASPMX2.GOOGLEMAIL.COM
9 ASPMX3.GOOGLEMAIL.COM
TXT
apple-domain-verification=dWEuc3QD1drF63mw
jamf-site-verification=2zGEDDZc4nEG2-v3AqjJ2w
teamviewer-sso-verification=c09867eeb8df407daf2f9f2faa1f1ff0
atlassian-sending-domain-verification=07892f94-42f7-456d-8d71-658cb159ff3d
google-site-verification=qkkgw2PIaLvDL1kaiQWLtXhZOMjIEuIBDniTgovw5pY
docusign=ce4296ab-d137-494c-9bbc-cb535330f2bc
anthropic-domain-verification-hp464q=gc3U5X4P1mSVaIXi3vJ2B92lI
atlassian-domain-verification=yVj1vr3Nr6tmy0V0lUUL6Gs30jrMkedjLqQ/lZaTA8saAUuHAB...
google-site-verification=CiBs0RoLAte45_0-L9je3UEVfrm_bT3wrdLLRHqzPBc
SPF v=spf1 ip4:128.117.0.0/16 ip4:192.43.244.0/24 ip4:192.52.106.0/24 ip4:128.171.19...
google-site-verification=gqqXpx_rqoCerglkRnAvZVUPP0oP3E_7MXCV0FoCg7w
google-site-verification=odg4HykylvAH1p_lmOGTpMzIeLze2nQESxDLeEW37xY
google-site-verification=WColASQtXu3yj2gC2cnYfJDtrcyBW3Cyl5YtO6_7DZs
cisco-ci-domain-verification=41c3e1d6b60ce5a8857f1070d854015d3a3305e24d4ffd4dc29...
vmware-cloud-verification-f853010c-0c8b-42cc-afab-c4008bde252b
CAALookup not available with standard resolver
Resolved in 370 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
Redirect Chain
1 redirect(s), 589 ms total
PASS
1 redirect(s), 589 ms total
Info::
Single redirect
Got: https://ucar.edu → https://www.ucar.edu/ (301)
Info::
WWW normalization redirect
Info::
Redirect overhead: 589 ms total
Got: 589 ms

https://ucar.edu

431 ms · HTTP/1.1

301

https://www.ucar.edu/

158 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ucar.edu301431 msHTTP/1.1Apache
2https://www.ucar.edu/200158 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 142 URLs
PASS
robots.txt present, sitemap with 142 URLs
Info::
robots.txt is present
Got: 2027 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 142 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 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 200 OK
Type URL Set URLs 142 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
ucar.edu — 40 years, 1 months old, hosted on UCAR-AS - University Corporation for Atmospheric Research, US
PASS
ucar.edu — 40 years, 1 months old, hosted on UCAR-AS - University Corporation for Atmospheric Research, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: UCAR-AS - University Corporation for Atmospheric Research, US
Got: AS194
Domain expiry

377 days

July 31, 2027

SSL certificate

276 days

Issued by Internet2

Domain age

40 years, 1 months

Registered October 3, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

UCAR-AS - University Corporation for Atmospheric Research, US

ASN AS194

128.117.225.32

Registrar

Registrar unknown

Lock status unknown 5 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created October 3, 1986 (40 years, 1 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated June 11, 2024
Name Servers dns.ucar.edu, dnsnx1.nwsc.ucar.edu, dnsx1.ucar.edu, dnsnx2.nwsc.ucar.edu, dnsx2.ucar.edu
Registrant University Corporation for Atmospheric Research
Hosting
IP Address 128.117.225.32
ASN AS194 (UCAR-AS - University Corporation for Atmospheric Research, US)
Provider UCAR-AS - University Corporation for Atmospheric Research, US
Data source: whois (2.0s)
A
HTTP Probe Timing
Total 578 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
141 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
143 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
151 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
578 ms
Total Time Total request time from DNS lookup through full response.
578 ms

Connection waterfall

DNS Lookup 141 ms TCP Connect 143 ms TLS Handshake 151 ms Server Processing 144 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