Skip to content
https://uark.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
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

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

Inconsistent — duplicate content risk

HTTP → HTTPS

307http://uark.edu/ → https://uark.edu/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

165
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, 310 ms lookup
PASS
1 A records, 310 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 23.98.151.49
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: ns3.uark.edu, ns1.uark.edu, ns2.uark.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 (310 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 310 ms
A23.98.151.49
AAAA—
CNAME—
NSns3.uark.edu, ns1.uark.edu, ns2.uark.edu
MX
0 uark-edu.mail.protection.outlook.com
TXT
paloaltonetworks-site-verification=3a844cc829f86b709477ee2315c3620efdfd1a60d804c...
1password-site-verification=OKJRC54EJ5HTVJFFBOUDTNWLS4
dell-technologies-domain-verification=uark.edu_caf993e3-c158-4330-993d-202ad808b...
openai-domain-verification=dv-ieRO583scEFa5oFLU9p4H8xy
atlassian-domain-verification=QT4whWl6jHCrM9lZ/639Y8fPTfb41TeCGCGEYECv83BebcNK8S...
canva-site-verification=-QlheyN_0PwepwShUfeRiQ
infoblox-domain-mastery=d941f56c0797346da0f7b2b4bce5dab4b3bc11c602765c1a88616a6c...
d365mktkey=cZualCMJupv8sWSLtaFYPlf3jWKOgjgj3aVnB2WcDAox
d365mktkey=xwiR1W0hNVTsZOxwocE0x8NY7kyZdujwKBzPhC6ItVIx
0ed1fe018a41f207336bdd40d6a2a63118a8b34467
apple-domain-verification=JBJP0AmvRNrmIEo4
docusign=0728cc21-b8db-4ffc-93e6-f0155a44fb50
cisco-ci-domain-verification=27fd8b09494fe78e837dc6e4576453690faad96617a752e3a13...
google-site-verification=bRBHwdbHsI5ZAbv4OOuWHqgGfZus8gjyOqqybpxTegk
google-site-verification=12gHWu5hiZJQDUpjQoTcVwiEyVXI2haSIoMlkWFTf6c
google-site-verification=SQ-gzhKjDLomGebtkTwZooU8BUM3cPGINrcZ-uKhg6g
pardot_184512_*=f23d0dc3d0866dc2ce6fcd6274ab965d3313ecadfae979454b8ac2a365d1b6ff
adobe-idp-site-verification=0d256ed9-dad4-4152-81fb-516fecb0e5ea
MS=ms53943966
SPF v=spf1 redirect=90jug4al._spf._d.mim.ec
67Gz9lADw8R1lzxcMjvKq/cAAOSX1NNL/m6sQg72QgenwFZqaz22O42spQ5hUc8ZG9u6pP1A5by6w3Ff...
CAALookup not available with standard resolver
Resolved in 310 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), 479 ms total
PASS
1 redirect(s), 479 ms total
Info::
Single redirect
Got: https://uark.edu → https://www.uark.edu/ (301)
Info::
WWW normalization redirect

https://uark.edu

196 ms · HTTP/1.1

301

https://www.uark.edu/

283 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://uark.edu301196 msHTTP/1.1Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k
2https://www.uark.edu/200283 msHTTP/1.1Apache/2.4.37 (Red Hat Enterprise Linux) OpenSSL/1.1.1k

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 32 URLs
PASS
robots.txt present, sitemap with 32 URLs
Info::
robots.txt is present
Got: 59 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 32 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 59 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /discover/*
Disallow: /_resources/*
sitemap.xml 200 OK
Type URL Set URLs 32 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
uark.edu — 37 years, 2 months old, hosted on Microsoft Azure
PASS
uark.edu — 37 years, 2 months old, hosted on Microsoft Azure
Info::
Domain registered until Jul 31, 2027 (1 years, 3 months remaining)
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

412 days

July 31, 2027

SSL certificate

165 days

Issued by Internet2

Domain age

37 years, 2 months

Registered August 31, 1989

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

23.98.151.49

Registrar

Registrar unknown

Lock status unknown 3 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Registrar
Created August 31, 1989 (37 years, 2 months ago)
Expires July 31, 2027 (1 years, 3 months)
Last Updated April 17, 2026
Name Servers ns2.uark.edu, ns3.uark.edu, ns1.uark.edu
Registrant University of Arkansas - Fayetteville
Hosting
IP Address 23.98.151.49
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: whois (0.3s)
A+
HTTP Probe Timing
Total 224 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
57 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
53 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
56 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
224 ms
Total Time Total request time from DNS lookup through full response.
225 ms

Connection waterfall

DNS Lookup 57 ms TCP Connect 53 ms TLS Handshake 56 ms Server Processing 58 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