Skip to content
https://ntv.co.jp

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
0
REVIEW
5
PASS
3
INFO
1
Probed from Sao Paulo, Brazil
301 Moved Permanently
Checks
9
3 PASS 5 REVIEW
B
Redirect Chain
1 redirect(s), 1990 ms total
REVIEW
1 redirect(s), 1990 ms total
Info::
Single redirect
Got: https://ntv.co.jp → https://www.ntv.co.jp/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1990 ms total
Got: 1990 ms

https://ntv.co.jp

1078 ms · HTTP/1.1

301

https://www.ntv.co.jp/

912 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://ntv.co.jp3011078 msHTTP/1.1CloudFront
2https://www.ntv.co.jp/200912 msHTTP/1.1AmazonS3

See the visual redirect chain in the HTTP Probe tab →

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.ntv.co.jp/
200https://ntv.co.jp/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://ntv.co.jp/ → https://ntv.co.jp/

Consistent

B
HTTP Probe Timing
Total 1194 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
317 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
291 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
293 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.19 s
Total Time Total request time from DNS lookup through full response.
1.19 s

Connection waterfall

DNS Lookup 317 ms TCP Connect 291 ms TLS Handshake 293 ms Server Processing 293 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
200 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

200
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
B
CDN & Delivery
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
REVIEW
AWS CloudFront (FunctionGeneratedResponse from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: KIX82-P4)
Got: x-amz-cf-id: 4FdBBikgcjDWrInu2TqTl5kvqMxvg8NhoJQmjnOSWwbx5BVtnxNcNw==
Info::
CDN cache status: FunctionGeneratedResponse from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status FunctionGeneratedResponse from cloudfront Evidence x-amz-cf-id: 4FdBBikgcjDWrInu2TqTl5kvqMxvg8NhoJQmjnOSWwbx5BVtnxNcNw==
A
DNS Records
2 A records, 463 ms lookup
PASS
2 A records, 463 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 13.224.138.16, 13.224.138.28
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2600:9000:21b6:8400:1a:f637:5300:93a1, 2600:9000:21b6:be00:1a:f637:5300:93a1
Info::
3 nameserver(s) configured
Got: ns020-casb398250048tm7.c.d-53.jp, ns020-casb398250048tm7.c.d-53.net, ns020-casb398250048tm7.c.d-53.info
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
Warning::
DNS resolution is slow (463 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 463 ms
A13.224.138.16, 13.224.138.28
AAAA2600:9000:21b6:8400:1a:f637:5300:93a1, 2600:9000:21b6:be00:1a:f637:5300:93a1
CNAME—
NSns020-casb398250048tm7.c.d-53.jp, ns020-casb398250048tm7.c.d-53.net, ns020-casb398250048tm7.c.d-53.info
MX
0 ntv-co-jp.mail.protection.outlook.com
TXT
google-site-verification=7QRcYXZLrd01fNgIzc4SMSiNE7ly7vD-AzBh0VoT5-o
google-site-verification=NapzBYlGHzuDrZTbOThI9yFOubVia6CGEHzcFMDatNo
google-site-verification=cRYzhZj1w58cBk0g7FW4IpDZljmA9nsMYtkTQt42P3A
google-site-verification=z8K24W4zXWfu_lH__t6t2mD8pNS-dOKJRttrk-Fw5vk
SPF v=spf1 include:nb1ewwaqw6.powerspf.com include:spf.protection.outlook.com ~all
CAALookup not available with standard resolver
Resolved in 463 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.

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+
IPv6 Readiness
IPv6 reachable (310 ms)
PASS
IPv6 reachable (310 ms)
Info::
IPv6 is configured and reachable at 2600:9000:21b6:8400:1a:f637:5300:93a1, 2600:9000:21b6:be00:1a:f637:5300:93a1
Got: 310 ms connect
IPv6 Ready
AAAA Records 2600:9000:21b6:8400:1a:f637:5300:93a1, 2600:9000:21b6:be00:1a:f637:5300:93a1 Connection Reachable (310 ms)
A+
Crawlability
robots.txt present, sitemap with 135 URLs
PASS
robots.txt present, sitemap with 135 URLs
Info::
robots.txt is present
Got: 306 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 135 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 306 B Sitemaps referenced 3 User-agents Google-CloudVertexBot, Googlebot, * Blocking No — crawling allowed
User-agent: Google-CloudVertexBot
Disallow: /3min/search/
Disallow: /search/

User-agent: Googlebot
Disallow: /3min/search/
Disallow: /search/

User-agent: *
Allow: /

sitemap: https://www.ntv.co.jp/sitemap_ntv.xml
sitemap: https://www.ntv.co.jp/news-sitemap.xml
sitemap: https://www.ntv.co.jp/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 135 entries Valid XML Yes
Sample URLs:
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.

Send Feedback