Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.

SCORE

GRADE

FIX

REVIEW

PASS

INFO

Probed from New York, United Stated

302 Found

Checks

1 PASS 6 REVIEW 1 FIX

CDN & Delivery

Action

No CDN detected

FIX

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.

Redirect Chain

1 redirect(s), 1091 ms total

REVIEW

1 redirect(s), 1091 ms total

Single redirect

Got: https://softbank.jp → https://www.softbank.jp/ (302)

WWW normalization redirect

Uses 302 (temporary) redirect

If permanent, use 301 instead.

Got: https://softbank.jp

Redirect overhead: 1091 ms total

Got: 1091 ms

https://softbank.jp

892 ms · HTTP/1.1

302

https://www.softbank.jp/

199 ms · HTTP/1.1 FINAL

#	URL	Status	Time	Protocol	Server
1	https://softbank.jp	302	892 ms	HTTP/1.1
2	https://www.softbank.jp/	200	199 ms	HTTP/1.1

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

IPv6 Readiness

Action

No IPv6 support

REVIEW

No IPv6 support

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

Crawlability

Action

robots.txt present, sitemap with 0 URLs

REVIEW

robots.txt present, sitemap with 0 URLs

robots.txt is present

Got: 10240 bytes

sitemap.xml is present

sitemap.xml contains invalid XML

Search engines may not be able to parse the sitemap. Fix XML validation errors.

sitemap.xml is empty — no URLs found

An empty sitemap provides no value. Add <url> entries for your pages.

robots.txt does not reference a sitemap

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Search engines may not be able to parse the sitemap. Fix XML validation errors.

Why this matters

An unparseable sitemap is silently ignored by Google — the URLs it advertises are never queued for crawl.

Learn more ▾

Google's sitemap parser is strict about XML validity. A single unescaped `&` or unclosed tag invalidates the whole file. Run your sitemap through a validator (Search Console's Sitemaps report flags it) and fix the offending entry. Most generators escape correctly; mistakes usually come from manually-written entries.

Source: sitemaps.org / Google Search Central

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more ▾

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK

Size 10240 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed





<!DOCTYPE html>

<html lang="ja">
<head>
    <!-- LayoutASitePC -->
    
    

    
    




    
    

<!-- =========== METADATA ============ -->
    <meta charset="UTF-8">
    <link rel="canonical" href="https://www.softbank.jp/">
<title>ソフトバンク</title>
<meta name="description" content="ソフトバンクの公式ホームページです。スマートフォンやインターネットなどライフスタイルを豊かにする各種サービスやAI・クラウドを含む多彩なソリューションなどを紹介しています。">
<meta name="keywords" content="SoftBank,ソフトバンク,スマートフォン,携帯電話,インターネット,固定電話,でんき,ネットワーク,法人向け事業,サステナビリティ,投資家情報,採用情報,AI,スポーツ">
    <meta property="og:title" content="ソフトバンク">
    <meta property="og:type" content="article">
    <meta property="og:description" content="ソフトバンクの公式ホームページです。スマートフォンやインターネットなどライフスタイルを豊かにする各種サービスやAI・クラウドを含む多彩なソリューションなどを紹介しています。">
    <meta property="og:url" content="https://www.softbank.jp/">
    <meta property="og:image" content="https://www.softbank.jp/site/set/common/shared/img/icon_softbank.gif">
    <meta property="og:site_name" content="ソフトバンク">
    <meta property="fb:app_id" content="378662655513103">
    <link rel="shortcut icon" href="/site/set/common/p/img/favicon.ico">


    
    
<!-- =========== /METADATA ============ -->
<!-- ========= COMMON IMPORT ========== -->
<script src="/-/media/sb/sjp/scassets/system/common/js/include.js"></script>

<script type="text/javascript">var nowDate = '20260422073938'</script>

<!-- OfficialTopLayout PC -->
<!-- Common Code -->
<meta name="viewport" content="width=1024">
<!-- /Common Code -->
<!-- ======== /COMMON IMPORT ========== -->
<!-- ========= LOCAL IMPORT =========== -->

<!--============ LOCAL IMPORT =============-->
<link rel="stylesheet" href="/site/set/common/shared/css/reset/reset-v2.css">
<link rel="stylesheet" href="/site/set/common/p/css/rf2017-ph1-print.css" media="print">
<link rel="stylesheet" href="/site/set/common/info/v1/p/css/index.css">
<link rel="stylesheet" href="/site/set/data/top/css/p/2026/index.css">
<link rel="stylesheet" href="/site/set/common/ticker/v3/p/css/index.css">
<noscript>
<link rel="stylesheet" href="/site/set/common/noscript/v1/p/css/index.css">
<link rel="stylesheet" href="/site/set/common/ticker/v3/p/css/noscript.css">
</noscript>

<!-- window.SB_PAGE.SW = 'false'; -->
<script>
window.SB_PAGE = window.SB_PAGE || {};
</script>

<script src="/site/set/common/shared/js/jquery-3.6.1.min.js" defer></script>
<script src="/site/set/data/top/js/p/2026/index.js" defer></script>
<script src="/site/set/common/info/v1/shared/js/index.js" defer></script>

<link rel="stylesheet" href="/site/set/data/top/css/p/2026/index.u96.css">
<link rel="stylesheet" href="/site/set/data/top/css/shared/2026/index.u96.css">
<script src="/site/set/data/top/js/p/2026/index.u96.js" defer></script>
<script src="/site/set/data/top/js/shared/2026/index.u96.js" defer></script>
<!--============= /LOCAL IMPORT ==============-->
<!-- ======== /LOCAL IMPORT =========== -->



    
    



</head>
<body>
    
    




    
    





    <div id="sb-appshell-v1" class="sb-appshell-v1">

        
        

<noscript>
<aside id="sb-appshell-v1-header-info" class="sb-appshell-v1-header-info">
<div class="noscript-layout">
<p class="noscript-layout_text">当ウェブサイトでは、JavaScriptを使用しています。ご使用のブラウザー設定においてJavaScriptをオン（有効）にしていただきますようお願いいたします。</p>
</div>
</aside>
</noscript><!-- Ticker -->





        

        <div id="sb-appshell-v1-container" class="sb-appshell-v1-container">
            <div id="sb-appshell-v1-contents" class="sb-appshell-v1-contents">

                <!--メイン共通トップ画面以外の場合はヘッダーパンくず表示-->

<!-- 災害用伝言版 (DisasterEmergencyMessage) -->


<div class="top-page-layout-mainvisual _ga_area_header">
    <div class="top-page-layout-mainvisual_inner">
        <!-- SBロゴ-->
                    <!--- SBロゴ PC --->
            <div class="top-page-layout-mainvisual_logo">
              <a href="/" class="top-page-layout-mainvisual_logo-link">
                <img src="/site/set/data/top/img/shared/2026/logo-sb-black.svg" alt="SoftBank"
                  class="top-page-layout-mainvisual_logo-image">
              </a>
            </div>
        <!-- SBロゴ下フリーエリア-->
                <!--- PC --->
<!-- SBロゴ下フリーエリア PC-->


        <!-- 災害用伝言板の追加-->
                <div class="section-info-disaster-container">
          <!-- 災害：高 -->
          <div class="section-info section-info-high section-info-attention">
            <div class="section-info-high-wrap">
              <aside class="section-info-high-disaster-lv2" data-version="2024a">
                <div class="section-info-high-disaster-lv2_header">
                  <div>
                    <span class="section-info-high-disaster-lv2_title">災害用伝言板</span>
                    <span class="section-info-high-disaster-lv2_title-en">Disaster Message Board</span>
                  </div>
                </div>
                <div class="section-info-high-disaster-lv2_contents">
                  <div class="section-info-high-disaster-lv2_link-area">
                    <a href="http://dengon.softbank.ne.jp/J" class="section-info-high-disaster-lv2_button">登録・確認する</a>
                    <a href="/mobile/service/dengon/boards/" class="section-info-high-disaster-lv2_usage-link">利用方法をみる</a>
                  </div>
                </div>
              </aside>
            </div>
          </div>
          <!-- / 災害：高 -->
        </div>

        <script src="/site/set/common/disaster/v2/shared/js/index.js"></script>
        <script>
          window.SB_PAGE.DISASTER_MAINVISUAL = true;
        </script>
        <!-- 大災害情報掲載枠-->
        <!-- 災害情報掲載枠 表示モード 大災害(PC)-->
<div class="section-info-catastrophe">
  <script src="/site/set/common/disaster/v2/shared/js/catastrophe.js?20250121"></script>
</div>

        <!-- サービス-->
        
    </div>
    <div class="top-page-icon-arrow-container">
        <span class="top-page-icon-arrow-container_item"></span>
        <span class="top-page-icon-arrow-container_item"></span>
    </div>
    <div id="visualizer-01">
        <div class="cover">
            <div class="shadow-top"></div>
            <div class="shadow-bottom"></div>
        </div>
        <div class="bg"></div>
    </div>
</div>


<!--重要なお知らせ-->


                    <main class="contents-area" role="main">
                        
                        <!--TopページのTOPICS部分-->



<!-- TOPICS部分-->
<section class="top-page-section-01">
    
    <div class="top-page-carousel-01">
        <div class="top-page-carousel-01-container">
            <div class="top-page-carousel-01_inner">
                <div class="top-page-carousel-01_list">

                    <div class="top-page-carousel-01_list-item" data-title="社会課題にアンサーを">
                      <a href="/corp/special/answer/" class="top-page-carousel-01_link" onclick="_ga.spotEvent('[MOBILE]_モバイル','tougou-top','ブランディングカルーセル｜1枠目')">
                        <img
                          data-src="/site/set/data/top/img/shared/2026/top-page-carousel-01_list-item-01.webp"
                          alt="未来を想い、いま動く。社会課題を解決する取り組みとは。"
                          class="top-page-carousel-01_image mainvisual-carousel_image js-copyguard">
                      </a>
                    </div>                    <div class="top-page-carousel-01_list-item" data-title="AI">
                      <a href="/biz/about/ai/" class="top-page-carousel-01_link" onclick="_ga.spotEvent('[MOBILE]_モバイル','tougou-top','ブランディングカルーセル｜2枠目')">
                        <img
                          data-src="/site/set/data/top/img/shared/2026/top-page-carousel-01_list-item-02.webp"
                          alt="AIはただの”道具”ではなく、もっと人に寄り添う存在へ。"
                          class="top-page-carousel-01_image js-copyguard"></a>
                    </div>                    <div class="top-page-carousel-01_list-item" data-title="NatureBank">
                      <a href="/naturebank/" class="top-page-carousel-01_link" onclick="_ga.spotEvent('[MOBILE]_モバイル','tougou-top','ブランディングカルーセル｜3枠目')">
                        <img
                          data-src="/site/set/data/top/img/shared/2026/top-page-carousel-01_list-item-03.webp"
                          alt="サービスを使うだけ。ソフトバンクの森づくりの仕組み。"
                          class="top-page-carousel-01_image mainvisual-carousel_image js-copyguard">
                      </a>
                    </div><div class="top-page-carousel-01_list-item" data-title="スポーツ">
  <a href="/mobile/special/sports/" class="top-page-carousel-01_link" onclick="_ga.spotEvent('[MOBILE]_モバイル','tougou-top','ブランディングカルーセル｜4枠目')">
    <img
      data-src="/site/set/data/top/img/shared/2026/bnr_sports20260410.webp"
      alt="ITの力でスポーツの喜びや感動を多くの人に伝えたい。"
      class="top-page-carousel-01_image mainvisual-carousel_image js-copyguard">
  </a>
</div>                    <div class="top-page-carousel-01_list-item" data-title="UTX">
                      <a href="/corp/philosophy/technology/special/utx/" class="top-page-carousel-01_link" onclick="_ga.spotEvent('[MOBILE]_モバイル','t

sitemap.xml 200 OK

Type URL Set URLs 0 entries Valid XML No

URL Variants

Action

www/non-www, trailing slash, HTTP→HTTPS

REVIEW

www/non-www, trailing slash, HTTP→HTTPS

Both www and non-www versions serve content

Got: Both variants return 200 Expected: One variant 301-redirects to the other

HTTP→HTTPS redirect uses 302 instead of 301

Got: 302 temporary redirect Expected: 301 permanent redirect

www / non-www

200https://www.softbank.jp/

200https://softbank.jp/

Inconsistent — duplicate content risk

HTTP → HTTPS

302http://softbank.jp/ → https://www.softbank.jp/

Use 301 (permanent) instead of 302 (temporary)

HTTP Probe Timing

Total 868 ms — DNS, TCP, TLS, TTFB, content transfer breakdown

REVIEW

DNS Lookup

187 ms

TCP Connect

170 ms

TLS Handshake

341 ms

Time to First Byte

868 ms

Total Time

868 ms

Connection waterfall

DNS Lookup 187 ms TCP Connect 170 ms TLS Handshake 341 ms Server Processing 170 ms Content Transfer 0 ms

TLS Certificate Expiry & Recommendations

98 days until leaf cert expires — 3 issues to address

REVIEW

Certificate validity

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, 190 ms lookup

PASS

1 A records, 190 ms lookup

Resolves to 1 IPv4 address(es)

Got: 20.89.86.42

Single A record — no DNS redundancy

Multiple A records provide failover if one server goes down.

No IPv6 (AAAA) records

3 nameserver(s) configured

Got: dns06.bbtec.net, dns03.bbtec.net, dns04.bbtec.net

No MX records — email not configured via DNS

CAA records not checked

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

SPF record present in TXT

DNS resolution time: 190 ms

Got: 190 ms

A	20.89.86.42
AAAA	—
CNAME	—
NS	dns06.bbtec.net, dns03.bbtec.net, dns04.bbtec.net
MX	—
TXT	google-site-verification=uzqGP9f1d542fpw7P3tYOMc9H-hRdAXLJIuJkGleWgA EVZ9lQLvUSjBQnKconAnt3qkihga6H iWlT2Aa5vfUwfckY6OvOWbAXFHhI5o google-site-verification=8IdUJQGvWGzOaEz2e6Ll5-DqgltHHOMV3sN5NjQB954 2NVVWuQQ2GFVTasqFQJXJg6W5Mlxna google-site-verification=X-H_4AZmNJARzxdjrsxLF-GxNXCKoa7WHymtCAqXjIs Q9NCHDH9VH8C0SUG9BSTOGCEJG pardot352851=0580bd860d365d991a7e03f0d2b29791f22b80abb77c9d9924c49c2decd1b27f nb7ei6Pnz85hW6utS9eZwQW9akTY43me0820_1200589 SPF v=spf1 a mx ip4:52.9.170.29 ip4:52.9.169.194 ip4:52.77.95.65 ip4:52.77.95.163 ip... google-site-verification=cSgY8bTpNITGP1wFDb0ntg36fdy7ZNW0VFtR9ferWx4 google-site-verification=BjJ4ydjl_BEycs7dMfL8ILeefyhUjklfssE5AE2kvPo
CAA	Lookup not available with standard resolver

Resolved in 190 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.

Domain Intelligence

Domain intelligence data not available

INFO

Domain intelligence data not available

RDAP and WHOIS lookup both failed

All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.