Skip to content
https://www.webasto.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
308 Permanent Redirect
Checks
17
8 PASS 9 REVIEW
B
DNS Records
4 A records, 24 ms lookup
REVIEW
4 A records, 24 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.3.10, 151.101.67.10, 151.101.131.10, 151.101.195.10
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: cdn.adobeaemcloud.com
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 24 ms
Got: 24 ms
A151.101.3.10, 151.101.67.10, 151.101.131.10, 151.101.195.10
AAAA
CNAMEcdn.adobeaemcloud.com
NS
MX
TXT
CAALookup not available with standard resolver
Resolved in 24 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 151.101.3.10: lookup 151.101.3.10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.67.10: lookup 151.101.67.10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.131.10: lookup 151.101.131.10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 151.101.195.10: lookup 151.101.195.10: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Redirect Chain
2 redirect(s), 220 ms total
REVIEW
2 redirect(s), 220 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

https://www.webasto.com

55 ms · HTTP/1.1

308

http://www.webasto.com/en-int.html

3 ms · HTTP/1.1

301

https://www.webasto.com/en-int.html

162 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.webasto.com30855 msHTTP/1.1
2http://www.webasto.com/en-int.html3013 msHTTP/1.1
3https://www.webasto.com/en-int.html200162 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

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
299 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

299
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
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 34ms across 3 resolvers (spread 15ms)
PASS
Mean 34ms across 3 resolvers (spread 15ms)
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
Info::
Cloudflare: 31ms
Got: 31ms via 1.1.1.1:53
Info::
Quad9: 43ms
Got: 43ms via 9.9.9.9:53
A+
Crawlability
robots.txt present, sitemap with 395 URLs
PASS
robots.txt present, sitemap with 395 URLs
Info::
robots.txt is present
Got: 804 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 395 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 804 B Sitemaps referenced 13 User-agents *, AdobeEdgeOptimize/1.0 Blocking No — crawling allowed
User-agent: *
Disallow: /content/webasto/language-masters/
Disallow: /*.pdf$
Disallow: /*.PDF$

User-agent: AdobeEdgeOptimize/1.0
Allow: /

Sitemap: https://www.webasto.com/en-int/sitemap.xml
Sitemap: https://www.webasto.com/de-de/sitemap.xml
Sitemap: https://www.webasto.com/de-at/sitemap.xml
Sitemap: https://www.webasto.com/en-us/sitemap.xml
Sitemap: https://www.webasto.com/nl-nl/sitemap.xml
Sitemap: https://www.webasto.com/fr-fr/sitemap.xml
Sitemap: https://www.webasto.com/it-it/sitemap.xml
Sitemap: https://www.webasto.com/ko-kr/sitemap.xml
Sitemap: https://www.webasto.com/en-in/sitemap.xml
Sitemap: https://www.webasto.com/es-es/sitemap.xml
Sitemap: https://www.webasto.com/ja-jp/sitemap.xml
Sitemap: https://www.webasto.com/tr-tr/sitemap.xml
Sitemap: https://www.webasto.com/zh-cn/sitemap.xml

A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.webasto.com/
301https://webasto.com/

Preferred variant: www

HTTP → HTTPS

301http://www.webasto.com/ https://www.webasto.com/

Consistent

A+
Domain Intelligence
webasto.com — via CSC Corporate Domains, Inc., 29 years, 6 months old, hosted on Fastly
PASS
webasto.com — via CSC Corporate Domains, Inc., 29 years, 6 months old, hosted on Fastly
Info::
Domain registered until Mar 15, 2027 (10 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: Fastly
Got: AS54113
Domain expiry

301 days

March 15, 2027

SSL certificate

299 days

Issued by Sectigo Limited

Domain age

29 years, 6 months

Registered March 14, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.195.10

Registrar

CSC Corporate Domains, Inc.

Unlocked 6 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 March 14, 1997 (29 years, 6 months ago)
Expires March 15, 2027 (10 months)
Last Updated March 11, 2026
Name Servers ns1.netnames.net, ns2.netnames.net, ns5.netnames.net, ns6.netnames.net, ns7.netnames.net, ns8.netnames.net
DNSSEC Not enabled
Hosting
IP Address 151.101.195.10
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.3s)

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

Connection waterfall

DNS Lookup 47 ms TCP Connect 0 ms TLS Handshake 5 ms Server Processing 118 ms Content Transfer 0 ms
A
CDN & Delivery
Fastly (MISS)
PASS
Fastly (MISS)
Info::
Site is served via Fastly CDN
Got: x-served-by: cache-toj-leto2350026-TOJ
Info::
CDN cache status: MISS
CDN Detected: Fastly
Provider Fastly Cache Status MISS Evidence x-served-by: cache-toj-leto2350026-TOJ
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 2 header(s)
Got: x-cache=MISS, x-served-by=cache-toj-leto2350026-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback