Infrastructure
· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.DCDN & DeliveryActionNo CDN detectedFIX
Consider using a CDN to improve global delivery speed and reduce origin load.
BRedirect Chain1 redirect(s), 1125 ms totalREVIEW
https://line.me
812 ms · HTTP/1.1
https://www.line.me/en/
314 ms · HTTP/1.1 FINAL
| # | URL | Status | Time | Protocol | Server |
|---|---|---|---|---|---|
| 1 | https://line.me | 302 | 812 ms | HTTP/1.1 | openresty |
| 2 | https://www.line.me/en/ | 200 | 314 ms | HTTP/1.1 | VOS |
See the visual redirect chain in the HTTP Probe tab →
If permanent, use 301 instead.
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
CIPv6 ReadinessActionNo IPv6 supportREVIEW
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.
Source: Google IPv6 stats
BCrawlabilityrobots.txt present, no sitemapREVIEW
A sitemap helps search engines discover and index your pages more efficiently.
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
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.
robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.
Source: sitemaps.org
User-agent: Twitterbot
Disallow: *
Allow: /ti/g2/
User-agent: Mediapartners-Google
Disallow: /app/
Disallow: /cs/
Disallow: /R/
Disallow: /ti/
Disallow: /msg/
Disallow: /au/
Disallow: /run/
Allow: /ti/p/
Allow: /R/ti/p/
Allow: /ti/g2/
Allow: /ads.txt
Allow: /app-ads.txt
User-agent: *
Disallow: /app/
Disallow: /cs/
Disallow: /R/
Disallow: /ti/
Disallow: /msg/
Disallow: /au/
Disallow: /run/
Allow: /ti/p/
Allow: /R/ti/p/
Allow: /ti/g/
Allow: /R/ti/g/
No sitemap found
Adding a sitemap helps search engines discover your pages.
BHTTP Probe TimingTotal 852 ms — DNS, TCP, TLS, TTFB, content transfer breakdownREVIEW
Connection waterfall
BTLS Certificate Expiry & Recommendations147 days until leaf cert expires — 5 issues to addressREVIEW
Certificate validity
Recommended actions
- Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
- 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
ADNS Records1 A records, 249 ms lookupPASS
| A | 147.92.243.206 |
| AAAA | — |
| CNAME | — |
| NS | ns1.naver.jp, ns2.naver.jp, ans2.linecorp.com, ans1.linecorp.com |
| MX | 10 mx-common.line-apps.com 100 mx1-common.line-apps.com 100 mx3-common.line-apps.com 100 mx2-common.line-apps.com |
| TXT | facebook-domain-verification=35wnsqkba1tqtxca6q5xlxrxcul4qd google-site-verification=Ri-G6bf49-iTkhhxR6TAWnk0_yfslPvcvsQrPa8Usvc SPF v=spf1 include:naver.com include:spf.naver.jp ip4:203.104.136.0/24 ip4:147.92.12... |
| CAA | Lookup not available with standard resolver |
Multiple A records provide failover if one server goes down.
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.
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.
DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.
Source: DNS performance benchmarks
A+URL Variantswww/non-www, trailing slash, HTTP→HTTPSPASS
www / non-www
Preferred variant: non-www
HTTP → HTTPS
Consistent
A+Domain Intelligenceline.me — via MarkMonitor Inc., 18 years, 2 months old, hosted on LINE LY Corporation, JPPASS
255 days
April 29, 2027
147 days
Issued by GlobalSign nv-sa
18 years, 2 months
Registered April 29, 2008
Status unknown
Protects against DNS spoofing
LINE LY Corporation, JP
ASN AS38631
147.92.243.206
MarkMonitor Inc.
Expiry timeline
Domain cannot be transferred without explicit unlock from the registrar. This protects against unauthorized transfers.
Registrar lock (clientTransferProhibited et al.) prevents unauthorized domain transfers — strongest defense against domain hijacking.
Source: ICANN / domain-security best practice