Skip to content
https://unt.edu

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
78
GRADE
C
FIX
2
REVIEW
3
PASS
4
INFO
0
Probed from Amsterdam, Netherlands
301 Moved Permanently
Checks
9
4 PASS 3 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1762 ms total
FIX
2 redirect(s), 1762 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
HTTP to HTTPS redirect present
Info::
WWW normalization redirect
Warning::
2-hop chain could be reduced to 1 hop
Redirect directly from https://unt.edu to https://www.unt.edu/
Warning::
Redirect overhead: 1762 ms total
Got: 1762 ms

https://unt.edu

484 ms · HTTP/1.1

301

http://www.unt.edu/

464 ms · HTTP/1.1

301

https://www.unt.edu/

814 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://unt.edu301484 msHTTP/1.1nginx/1.18.0 (Ubuntu)
2http://www.unt.edu/301464 msHTTP/1.1Microsoft-Azure-Application-Gateway/v2
3https://www.unt.edu/200814 msHTTP/1.1nginx/1.18.0 (Ubuntu)

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

Redirect directly from https://unt.edu to https://www.unt.edu/

Why this matters

Redirect chain could be flattened to one hop — server config tweak removes intermediate latency.

Source: web.dev

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

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

135
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, 730 ms lookup
PASS
1 A records, 730 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 172.202.165.49
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: ns-a.public.grid.untsystem.edu, ns-b.public.grid.untsystem.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 (730 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 730 ms
A172.202.165.49
AAAA—
CNAME—
NSns-a.public.grid.untsystem.edu, ns-b.public.grid.untsystem.edu
MX
0 unt-edu.mail.protection.outlook.com
TXT
MS=ms17734452
apple-domain-verification=odyTchJ0Zep4KXf8
docusign=ed7ba2ec-2455-46a0-b972-e7f7563a8a5e
jamf-site-verification=XNe3GXO303nQt1LTi_hU3A
zoho-verification=zb97372407.zmverify.zoho.com
autodesk-domain-verification=2vsnN_Pe9hZn4xmucaXJ
autodesk-domain-verification=bcXxGJAPD0MXKNJ-nuXS
airtable-verification=2ba0fc82009f730a4931c24b768ec227
knowbe4-site-verification=0dde97b504d7a03659ee3633d6fdf79d
onetrust-domain-verification=85f4cbbdcf16439a8c41bb8e2547a163
perplexity-ai-domain-verification-2kcba5=5SSj3loASzKMvjTu2dOACqxE2
google-site-verification=5KF2fknjwx6C8ylftwfQyMfXKahpR6Rol7vk3vVbv_Q
SPF v=spf1 ip4:129.120.248.128/26 ip4:129.120.82.19 include:spf.protection.outlook.c...
P3z6M1LZqdOGsejtZprWTkdjguDpW40sEvV3PegimdfVRxewQyMwoJXahoSns/Z+Nh+spm3v6D8eV/Sb...
j/DcLYqRuioL5fhK66DQDmrrK5wGQNeZgMQsmrT4YygAwQPlpC9T34lNwB3v3Ff3EV3tDTwy6qqgHUIN...
adobe-idp-site-verification=1737efadef3a28bae1283947c186bff7ce2b0fa0fd5341ae0efe...
atlassian-domain-verification=O6ac35acZSB73wXJE7KknW8wjYf8hD8NlMl2BIUAuV8PcOIa3i...
CAALookup not available with standard resolver
Resolved in 730 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 2857 URLs
PASS
robots.txt present, sitemap with 2857 URLs
Info::
robots.txt is present
Got: 519 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2857 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 519 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /archive/
Disallow: /_archive/
Disallow: /_dev/
Disallow: /_migration_www/
Disallow: /_resources/
Disallow: /_showcase/
Disallow: /ou-alerts/
Disallow: /ubsc_testing_site/
Disallow: /admissions/archive/
Disallow: /admissions/dev/
Disallow: /admissions/dev-1/
Disallow: /admissions/contact-us/archive/
Disallow: /academics/_archive/
Disallow: /success/_archived/
Disallow: /news/
Disallow: /_enrollment-dev/
Disallow: /strategic-plan/_dev/
Disallow: /*/_

Sitemap: https://www.unt.edu/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 2857 entries Valid XML Yes
Sample URLs:
A+
Domain Intelligence
unt.edu — 40 years, 1 months old, hosted on Microsoft Azure
PASS
unt.edu — 40 years, 1 months old, hosted on Microsoft Azure
Info::
Domain registered until Jul 31, 2026 (3 months remaining)
Info::
Hosting: Microsoft Azure
Got: AS8075
Domain expiry

47 days

July 31, 2026

SSL certificate

135 days

Issued by Internet2

Domain age

40 years, 1 months

Registered September 29, 1986

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

172.202.165.49

Registrar

Registrar unknown

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
Registrar
Created September 29, 1986 (40 years, 1 months ago)
Expires July 31, 2026 (3 months)
Last Updated September 3, 2025
Name Servers ns-a.public.grid.untsystem.edu, ns-b.public.grid.untsystem.edu
Registrant University of North Texas
Hosting
IP Address 172.202.165.49
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: whois (0.8s)
A
HTTP Probe Timing
Total 481 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
125 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
117 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
118 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
481 ms
Total Time Total request time from DNS lookup through full response.
481 ms

Connection waterfall

DNS Lookup 125 ms TCP Connect 117 ms TLS Handshake 118 ms Server Processing 121 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