Skip to content
https://f5.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Singapore, Singapore
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.f5.com/
200https://f5.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://f5.com/ https://f5.com/

Consistent

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

Certificate validity

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

Recommended actions

  • Add includeSubDomains to the HSTS directive
  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 1015 ms lookup
PASS
1 A records, 1015 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 159.60.134.0
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: pdns131.f5.com, pdns150.f5.com, pdns151.f5.com, pdns130.f5.com
Info::
2 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 (1015 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1015 ms
A159.60.134.0
AAAA
CNAME
NSpdns131.f5.com, pdns150.f5.com, pdns151.f5.com, pdns130.f5.com
MX
10 mx1.hc5801-97.iphmx.com
10 mx2.hc5801-97.iphmx.com
TXT
adobe-idp-site-verification=9af818c65525c17f45bb3b16b01b1292a6deed65c3f1f2b5815d...
cisco-ci-domain-verification=6a1e8be23a89b503b322d717459a6e8485a5875162146fb1b75...
atlassian-domain-verification=P1MVRYjo3N9ccfO1UcT5dJ6/Kgk15DSGNlWDMwnLtKrkvMEiLe...
SPF v=spf1 ip4:173.193.210.32/27 ip4:50.23.218.192/27 ip4:174.37.226.64/27 ip4:208.4...
MS=ms50853128
lucid-verification=58MzWUiZFz40
dropbox-domain-verification=oj5aqbo1eulz
apple-domain-verification=WmWqjjQdNTd8FLj1
status-page-domain-verification=y2kv019j5p4h
docusign=a0f80b2b-cad3-42fb-bec6-e6abf458700f
jamf-site-verification=YK2eaJK5WmX6OkUBJg-odw
docker-verification=b6850f2c-29d1-4ef5-9e84-06517c63b5b7
axios-domain-verification-pzeb04=jH6MgIXTf5a6SQ4sZ3dORRFkI
mongodb-site-verification=EGjovmxIH7GXJAXqy2EvL4YAZQYrNeE3
smartsheet-site-validation=ViznRSiRmJJYL_bUbM12TuSMi223D6i0
onetrust-domain-verification=305089a3e57b4f8087cf72e441a0c2c7
anthropic-domain-verification-2kamjp=ZZuMkVekozcvGxsCWJLdA1eAO
google-site-verification=cNGL-u4aLQubC64AY7ijWgQfdQP37Uc0iNF0L9CU-6Q
google-site-verification=nUmUWQAnvixEM-Lopr4DWotRA_VPJXL9YaCvt7e2odU
google-site-verification=o76ulVr4EPgPrnnF_bbHT1OL-9awsJWyZ9fkXHOL_Ks
google-site-verification=zIm-_CbdIdyLUQqG3LDYpyo--Hls4FaOjiJHmJ3-Jks
parkable-domain-verification=81BB0RfEy-pskwMf66KW26gEo68UYrZ4uYPpJIiUgoI=
0ugFx1int1d0kBtTIwKeL+3TA/tpJDPOm6BIWTRhDwKq9sj2Lc1loQ4tH27Da1vtpI1HjBxX2eHtpmEO...
access-domain-verification=991a9590d7b277fbfa4447d0a11a82014650d68747b1f81d75cd1...
Dynatrace-site-verification=14970c01-b9a2-4fb0-baa4-3e55421d6198__hjigvhh8rdsjed...
CAALookup not available with standard resolver
Resolved in 1015 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), 495 ms total
PASS
1 redirect(s), 495 ms total
Info::
Single redirect
Got: https://f5.com → https://www.f5.com/ (301)
Info::
WWW normalization redirect

https://f5.com

224 ms · HTTP/1.1

301

https://www.f5.com/

271 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://f5.com301224 msHTTP/1.1volt-adc
2https://www.f5.com/200271 msHTTP/1.1volt-adc

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 11 URLs
PASS
robots.txt present, sitemap with 11 URLs
Info::
robots.txt is present
Got: 156 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 11 entries
Info::
Sitemap index with 11 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 156 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
# *
User-agent: *
Allow: /

# Host
Host: https://www.f5.com

# Sitemaps
Sitemap: https://www.f5.com/sitemap.xml
Sitemap: https://www.f5.com/labs/sitemap.xml
A
Domain Intelligence
f5.com — via CSC Corporate Domains, Inc., 30 years, 3 months old, hosted on F5, FR
PASS
f5.com — via CSC Corporate Domains, Inc., 30 years, 3 months old, hosted on F5, FR
Warning::
Domain expires in 43 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 30, 2026
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: CSC Corporate Domains, Inc.
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: F5, FR
Got: AS35280
Domain expiry

EXPIRED

May 30, 2026

SSL certificate

235 days

Issued by Sectigo Limited

Domain age

30 years, 3 months

Registered May 31, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

F5, FR

ASN AS35280

159.60.134.0

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created May 31, 1996 (30 years, 3 months ago)
Expires May 30, 2026 (1 months)
Last Updated May 26, 2025
Name Servers pdns130.f5.com, pdns131.f5.com, pdns150.f5.com, pdns151.f5.com
DNSSEC Not enabled
Hosting
IP Address 159.60.134.0
ASN AS35280 (F5, FR)
Provider F5, FR
Data source: rdap (0.7s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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 225 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
177 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
8 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
225 ms
Total Time Total request time from DNS lookup through full response.
225 ms

Connection waterfall

DNS Lookup 177 ms TCP Connect 1 ms TLS Handshake 8 ms Server Processing 39 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