Skip to content
https://ufl.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
81
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), 1077 ms total
REVIEW
1 redirect(s), 1077 ms total
Info::
Single redirect
Got: https://ufl.edu → https://www.ufl.edu/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1077 ms total
Got: 1077 ms

https://ufl.edu

363 ms · HTTP/1.1

301

https://www.ufl.edu/

713 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ufl.edu301363 msHTTP/1.1Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k mod_fcgid/2.3.9
2https://www.ufl.edu/200713 msHTTP/1.1Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k mod_fcgid/2.3.9

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

290
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, 598 ms lookup
PASS
1 A records, 598 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 128.227.36.35
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
3 nameserver(s) configured
Got: ens.name.ufl.edu, ns.name.ufl.edu, rns.name.ufl.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 (598 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 598 ms
A128.227.36.35
AAAA—
CNAME—
NSens.name.ufl.edu, ns.name.ufl.edu, rns.name.ufl.edu
MX
5 ufl-edu.mail.protection.outlook.com
TXT
SPF v=spf1 include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email ~all
00DKb000000NtBp=1TBcx00000000T3
contractworksverify=M4WEJZvXFi
docusign=0db0a018-ba63-4181-91d0-cd9c16f19353
apple-domain-verification=cezqOSiI9SK9a4wl
e2ma-verification=4m3bb
xxxk+e03DboyMHBP94u1+9I0M/OW2MhnhvY1mCH5qTZ4LwHFLoDZsYbKIFtXbzD8b30PNIg3l8CTFPD+...
airtable-verification=a82914a4245481b0b3a7a97e4a705f9f
sending_domain1040741=8bf6473f43a280b921d387d953b46c40b1a5b21943f7cf17156d3ce141...
apple-domain-verification=y9JdzsvfpOAMTGJk
sending_domain307541=4424c706e483069c43c6b4d7013b71880610f4550a9125cef87ad1dda0a...
inLdNbkwVgpckGyQO5okUjF8D0uJZ3RAdXAJmuxIrII41wr60ds87xcnR1hL4gt60YCoqDHoQKAu7fdb...
00D41000002ElGo=1TBVm00000000Cv
adobe-idp-site-verification=7c8cd6e9c9b04eb60670818ca42e481ef6aa772e3c018fb8e967...
google-site-verification=WfK3GDL7G43-eS-CZkpODatU5zNZ6bMGegsicpPy6jo
sending_domain1069012=4f6b6aa09fc64566f0e8543c547d5eb4eb669afc5e1ac4a67fbcadcabc...
autodesk-domain-verification=FSF_3IyYoDsnRCfQp8Vo
google-site-verification=nXH7dAjpfCeP_T76cRDlE8-YIZk0FnYnyNLbR_-kFnk
MS=ms94919362
iContact180071
dropbox-domain-verification=1rzguf6ktomp
canva-site-verification=rqdZ_DiKQrp-Yu0_ubEY6g
airtable-verification=870ad782476d95a951486604523b909c
sending_domain134441=a48964708126d03db8f9f04ab520ac1c5316517fa7bea38b87d99947538...
cisco-ci-domain-verification=3f35d7a18857086c23bb36cdd19f3cd0cc81fdec4e9565954ac...
CAALookup not available with standard resolver
Resolved in 598 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 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 213 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 213 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *


Disallow: /wp-admin/

Disallow: /?page_id=5811&preview=true

Disallow: /xmlrpc.php

Disallow: /readme.html

Disallow: /refer/

Disallow: /cgi-bin/


Sitemap: https://www.ufl.edu/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
ufl.edu — 40 years, 7 months old, hosted on NERDCNET - University of Florida, US
PASS
ufl.edu — 40 years, 7 months old, hosted on NERDCNET - University of Florida, US
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: NERDCNET - University of Florida, US
Got: AS6356
Domain expiry

384 days

July 31, 2027

SSL certificate

290 days

Issued by Internet2

Domain age

40 years, 7 months

Registered March 25, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

NERDCNET - University of Florida, US

ASN AS6356

128.227.36.35

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created March 25, 1986 (40 years, 7 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated August 18, 2025
Name Servers rns.name.ufl.edu, ens.name.ufl.edu
Registrant University of Florida
Hosting
IP Address 128.227.36.35
ASN AS6356 (NERDCNET - University of Florida, US)
Provider NERDCNET - University of Florida, US
Data source: whois (0.8s)
A
HTTP Probe Timing
Total 504 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.
121 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
504 ms
Total Time Total request time from DNS lookup through full response.
504 ms

Connection waterfall

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