Skip to content
https://yamaha.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
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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.

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
Crawlability
no robots.txt, no sitemap
REVIEW
no robots.txt, no sitemap
Info::
No robots.txt found
robots.txt is optional but recommended. It tells search engine crawlers which pages to index.
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.

robots.txt is optional but recommended. It tells search engine crawlers which pages to index.

Why this matters

No robots.txt — crawlers fetch /robots.txt and get 404; not breaking but means default crawl behavior with no directives or sitemap reference.

Learn more

A minimal robots.txt with `User-agent: * / Allow: / / Sitemap: https://example.com/sitemap.xml` covers the basics. Without it, crawlers behave fine but lose the sitemap signal and can't be selectively blocked from crawl-traps.

Source: robotstxt.org

A sitemap helps search engines discover and index your pages more efficiently.

Why this matters

No sitemap.xml — Google relies on crawl-graph discovery alone, slowing indexing of deep or fresh URLs.

Learn more

A sitemap accelerates Google's discovery of new and updated content. Most CMSes auto-generate one; static-site frameworks need a build-step plugin. Reference it from robots.txt and submit in Search Console to confirm Google can fetch it.

Source: sitemaps.org / Google Search Central

robots.txt No robots.txt found

No robots.txt found

This is fine for most sites — a missing robots.txt allows all crawling by default.

sitemap.xml No sitemap found

No sitemap found

Adding a sitemap helps search engines discover your pages.

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 301 Expected: 301 redirect to HTTPS

www / non-www

403https://www.yamaha.com/
200https://yamaha.com/

HTTP → HTTPS

301http://yamaha.com/ http://www.yamaha.com/

HTTP version does not redirect to HTTPS

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

Certificate validity

64
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
4 A records, 33 ms lookup
PASS
4 A records, 33 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 216.239.32.21, 216.239.38.21, 216.239.34.21, 216.239.36.21
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-994.awsdns-60.net, ns-161.awsdns-20.com, ns-1033.awsdns-01.org, ns-1633.awsdns-12.co.uk
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: 33 ms
Got: 33 ms
A216.239.32.21, 216.239.38.21, 216.239.34.21, 216.239.36.21
AAAA
CNAME
NSns-994.awsdns-60.net, ns-161.awsdns-20.com, ns-1033.awsdns-01.org, ns-1633.awsdns-12.co.uk
MX
5 yamaha-com.mail.protection.outlook.com
TXT
google-site-verification=__XbOCSOsXMq8YyocHsQ-nSXl4DplHluDOFLd219jVg
wrike-verification=MTE1NTQyMTpmOGQ0ZTI4Yjk3NDIzYmZmMzMxMjMyN2Y5Mjc3OTljOGIxN2Y0M...
facebook-domain-verification=fb3zy49pax6m8in90yhpu2ch7jyaf9
qxUaB0DP/bnvbHflfBqCFvdjHqfs4zB0fqSmjH2gcgO7ViKyao86eKtET3ogbk6IWBHbAgk1MhgkH5y/...
pardot414612=d3da815cda662599e584f8d7370c2091f69a79fa642ef5f0aa0e09512fb93a60
00D300000000F1z=1TBPZ00000000jB
p295nkp7onb0g1mdqro3abrtkb
SPF v=spf1 mx include:_spf.salesforce.com include:spf.protection.outlook.com include...
google-site-verification=-Ohb368f9t5L3BqxYhqXD_kHTstCcCYsi0tiecsKwl0
adobe-idp-site-verification=6075f3826fc529e44a00891c89878a768e0d94fe72858fc5ee1e...
atlassian-domain-verification=bagOg1pjViKVz1kIe/YM//3XkAk/BcKHULqlqFZOE6z65uGIdA...
google-site-verification=-Uk6f3j6cJRIrYP-LsN9oCisl8SOXX9EQDXBiXSwNLw
CAALookup not available with standard resolver
Resolved in 33 ms

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
Redirect Chain
1 redirect(s), 353 ms total
PASS
1 redirect(s), 353 ms total
Info::
Single redirect
Got: https://yamaha.com → http://www.yamaha.com/ (301)
Info::
WWW normalization redirect

https://yamaha.com

291 ms · HTTP/1.1

301

http://www.yamaha.com/

62 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://yamaha.com301291 msHTTP/1.1Google Frontend
2http://www.yamaha.com/40362 msHTTP/1.1AkamaiGHost

See the visual redirect chain in the HTTP Probe tab →

A+
Domain Intelligence
yamaha.com — via 1API GmbH, 31 years, 11 months old, hosted on Google Cloud
PASS
yamaha.com — via 1API GmbH, 31 years, 11 months old, hosted on Google Cloud
Info::
Domain registered until Sep 7, 2026 (4 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: 1API GmbH
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: Google Cloud
Got: AS15169
Domain expiry

51 days

September 7, 2026

SSL certificate

64 days

Issued by Google Trust Services

Domain age

31 years, 11 months

Registered November 1, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS15169

216.239.38.21

Registrar

1API GmbH

Unlocked 4 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
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar 1API GmbH
Created November 1, 1994 (31 years, 11 months ago)
Expires September 7, 2026 (4 months)
Last Updated November 21, 2025
Name Servers ns-1033.awsdns-01.org, ns-161.awsdns-20.com, ns-1633.awsdns-12.co.uk, ns-994.awsdns-60.net
DNSSEC Not enabled
Hosting
IP Address 216.239.38.21
ASN AS15169 (GOOGLE - Google LLC, US)
Provider Google Cloud
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 336 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
39 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
16 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
26 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
337 ms
Total Time Total request time from DNS lookup through full response.
337 ms

Connection waterfall

DNS Lookup 39 ms TCP Connect 16 ms TLS Handshake 26 ms Server Processing 256 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