Skip to content
https://ukri.org

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 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), 1883 ms total
REVIEW
1 redirect(s), 1883 ms total
Info::
Single redirect
Got: https://ukri.org → https://www.ukri.org/ (302)
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://ukri.org
Warning::
Redirect overhead: 1883 ms total
Got: 1883 ms

https://ukri.org

575 ms · HTTP/1.1

302

https://www.ukri.org/

1308 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ukri.org302575 msHTTP/1.1
2https://www.ukri.org/2001308 msHTTP/1.1Apache/2.4.62 (Debian)

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.ukri.org/
200https://ukri.org/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://ukri.org/ https://ukri.org/

Use 301 (permanent) instead of 302 (temporary)

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

Certificate validity

69
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, 25 ms lookup
PASS
1 A records, 25 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 149.155.59.247
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info
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
Info::
DNS resolution time: 25 ms
Got: 25 ms
A149.155.59.247
AAAA
CNAME
NSns1-01.azure-dns.com, ns2-01.azure-dns.net, ns3-01.azure-dns.org, ns4-01.azure-dns.info
MX
2 ukri-org.mail.protection.outlook.com
TXT
4aa7f78b-78a7-43f1-845c-b380d71cb7e3_210918
atlassian-domain-verification=ojyWRYak1smqDGoMaYmjxlUW4GiRoX1fLzpINepDYxazdXxnR6...
asv=1343ed51bcdfbc507e36c3e2bace2ddb
lucid-verification=<1kpWfDrQBJJVxCfN2QU2>
miro-verification=fcc69ce138a4dfc657db079ee981e2c3bcfe7bf1
onetrust-domain-verification=db7d7aaa33d346b0a7512146d205043f
box-domain-verification=048eb4b924043d41b665496e720c43f8f5fd451a5c1c19fb4f083a5d...
F209AA29-3FB4-4352-A030-FCA3A9CB16B5
b2d0dce5-745a-4615-a2aa-2a11d15ea1e7_020718
dc8cf403-4895-4d90-b149-c0317a7ce4d7_030818
ulc07nda956sgl98cj4kap1odk
9qgetgpjrgh3lcghinpn5en9fm
MS=ms40598386
google-site-verification=csikO-EDOkPpkA2FBW_yxwwzdedUYaq4vGNp1DNbyJE
google-site-verification=4MJK2v88w045AqgIQUfAmDwRFcStfnr2E4Q0__ncQfI
apple-domain-verification=5L3Xaaxs34ByiFYW
amazonses:AdLeVhWLXJl1NEBbOobMCKZkB3ZdXO+6GEK2PUHVKcU=
cisco-ci-domain-verification=48e4b32c125ffbf9aa9bec1cfdb91a3be42193468bd2d968392...
SPF v=spf1 include:spf.protection.outlook.com include:servers.mcsv.net include:spf.e...
CAALookup not available with standard resolver
Resolved in 25 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 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 110 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
Sitemap index with 12 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 110 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.ukri.org/sitemap.xml

A+
Domain Intelligence
ukri.org — via IONOS SE, 16 years old, hosted on JANET Jisc Services Limited, GB
PASS
ukri.org — via IONOS SE, 16 years old, hosted on JANET Jisc Services Limited, GB
Info::
Domain registered until Jun 20, 2028 (2 years, 2 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: IONOS SE
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: JANET Jisc Services Limited, GB
Got: AS786
Domain expiry

738 days

June 20, 2028

SSL certificate

69 days

Issued by Let's Encrypt

Domain age

16 years

Registered June 20, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

JANET Jisc Services Limited, GB

ASN AS786

149.155.59.247

Registrar

IONOS SE

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar IONOS SE
Created June 20, 2010 (16 years ago)
Expires June 20, 2028 (2 years, 2 months)
Last Updated December 5, 2025
Name Servers ns3-01.azure-dns.org, ns1-01.azure-dns.com, ns2-01.azure-dns.net, ns4-01.azure-dns.info
DNSSEC Not enabled
Hosting
IP Address 149.155.59.247
ASN AS786 (JANET Jisc Services Limited, GB)
Provider JANET Jisc Services Limited, GB
Data source: rdap (0.5s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A
HTTP Probe Timing
Total 574 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
11 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
183 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
197 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
574 ms
Total Time Total request time from DNS lookup through full response.
574 ms

Connection waterfall

DNS Lookup 11 ms TCP Connect 183 ms TLS Handshake 197 ms Server Processing 184 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