Skip to content
https://skf.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
82
GRADE
B
FIX
2
REVIEW
2
PASS
5
INFO
0
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
5 PASS 2 REVIEW 2 FIX
D
Redirect Chain
Action
2 redirect(s), 1004 ms total
FIX
2 redirect(s), 1004 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1004 ms total
Got: 1004 ms

https://skf.com

745 ms · HTTP/1.1

301

https://www.skf.com/

219 ms · HTTP/1.1

307

https://www.skf.com/br

39 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://skf.com301745 msHTTP/1.1Microsoft-Azure-Application-Gateway/v2
2https://www.skf.com/307219 msHTTP/1.1
3https://www.skf.com/br20039 msHTTP/1.1

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

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
TLS Certificate Expiry & Recommendations
323 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

323
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, 1627 ms lookup
PASS
1 A records, 1627 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 20.86.182.89
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: dns02.skf.com, dns01.skf.com
Info::
3 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 (1627 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1627 ms
A20.86.182.89
AAAA—
CNAME—
NSdns02.skf.com, dns01.skf.com
MX
1 skf-com.mail.protection.outlook.com
5 skf-com.mail.protection.outlook.com
10 skf-com.mail.protection.outlook.com
TXT
uber-domain-verification=b99e5594-4402-47f0-92c7-2a22ab94c2a6
t5mrm80ovoljpdtsatv7tdk12t
miro-verification=68eec0d88e75209601f6240f2e74c96c57cddb72
DomainVerification=OEOW5VKXN8XPFRAV8899BJD1TNH8E3X29XHE8PKE1P36AN258F6AN27IMDQAZ...
apple-domain-verification=tnC5wKsLJRF23VXi
flexera-domain-verification-geuwzvklswerlshu
google-site-verification=kgR8tfGeRLrmWzWy_LqmyCaMcnpQeRXu7AZIiWmmGWY
SPF v=spf1 include:spf.protection.outlook.com include:spf1.skf.com include:spf2.skf....
teamviewer-sso-verification=e1c7d81fb7614d19960cbd9280f1e31f
google-site-verification=JbrkbFl-BuOAoxwkRqlyjZG11xyg2zLvMGji9558AE8
facebook-domain-verification=6u0xy2nng07p6l8rfx13hkl4vll7ve
docusign=bd60fc9e-aa4e-43b3-853e-67e26923a7db
amazonses:ZQGmSn7pjHvvqHSxwDrJa4D0yoMlQoqRKLWQDPc/xTg=
mongodb-site-verification=IpeFNhKMYfPZoWagubug14fofWlBfdO4
docusign=fe900b11-0626-4cf0-afc7-ac50ebfe8157
amazonses:zE4iwURHgPvLqIJNuS21kiO/8HrDEcTsD8MkoflmnfI=
v=DMARC1; p=none; rua=mailto:1b366b67d329107@rep.dmarcanalyzer.com; ruf=mailto:1...
vmware-cloud-verification-374b9805-21a3-4bbf-b074-87a5b60d6d0a
infor-cloudsuite-domain-verification=JPLUXV2SDW5V6XFA57YM7L4PTYY3T5DEY32ZNETGRSU...
CAALookup not available with standard resolver
Resolved in 1627 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 122 URLs
PASS
robots.txt present, sitemap with 122 URLs
Info::
robots.txt is present
Got: 740 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 122 entries
Info::
Sitemap index with 122 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 740 B Sitemaps referenced 2 User-agents Applebot, Seekport Crawler, *, Semrushbot-SA, bingbot Blocking No — crawling allowed
User-agent: *

Disallow: /*/myskf.app
Disallow: /*/to-be-deleted/
Disallow: /*/overlay-panels/
Disallow: /*/authorized-general/
Disallow: /*/authorised-general/
Disallow: /*/certified-rebuilder/
Disallow: /files/*.pdf$
Disallow: /*.jsp$
Disallow: /*.jsp?
Disallow: /eu/
Disallow: /nam/
Disallow: /group/test/
Disallow: /*/windcustomers/
Disallow: /*/simproexpert/
Disallow: /*/nestle/
Disallow: /*/simproquick/
Disallow: /*/staging-only/

Sitemap: https://www.skf.com/sitemap/productsitemap/sitemap_products_index.xml
Sitemap: https://www.skf.com/sitemap_index.xml

Host: www.skf.com

User-agent: Semrushbot-SA
Crawl-delay: 1

User-agent: bingbot
Crawl-delay: 1

User-agent: Applebot
Crawl-delay: 1

User-agent: Seekport Crawler
Disallow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 122 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

307https://www.skf.com/
200https://skf.com/

HTTP → HTTPS

301http://skf.com/ → https://www.skf.com/

Consistent

A+
Domain Intelligence
skf.com — via CSC Corporate Domains, Inc., 29 years, 9 months old, hosted on Microsoft Azure
PASS
skf.com — via CSC Corporate Domains, Inc., 29 years, 9 months old, hosted on Microsoft Azure
Info::
Domain registered until Dec 2, 2026 (7 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: 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: Microsoft Azure
Got: AS8075
Domain expiry

171 days

December 2, 2026

SSL certificate

323 days

Issued by Sectigo Limited

Domain age

29 years, 9 months

Registered December 3, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Microsoft Azure

ASN AS8075

20.86.182.89

Registrar

CSC Corporate Domains, Inc.

Unlocked 2 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 CSC Corporate Domains, Inc.
Created December 3, 1996 (29 years, 9 months ago)
Expires December 2, 2026 (7 months)
Last Updated November 28, 2025
Name Servers dns01.skf.com, dns02.skf.com
DNSSEC Not enabled
Hosting
IP Address 20.86.182.89
ASN AS8075 (MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation, US)
Provider Microsoft Azure
Data source: rdap (0.8s)

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

Connection waterfall

DNS Lookup 195 ms TCP Connect 181 ms TLS Handshake 186 ms Server Processing 181 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