Skip to content
https://qiita.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
98
GRADE
A+
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
9
7 PASS 2 REVIEW
C
HTTP Probe Timing
Action
Total 1707 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
134 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
2 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.45 s
Total Time Total request time from DNS lookup through full response.
1.71 s

Connection waterfall

DNS Lookup 134 ms TCP Connect 2 ms TLS Handshake 4 ms Server Processing 1.31 s Content Transfer 258 ms
B
TLS Certificate Expiry & Recommendations
163 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

163
days left
0d 30d 60d 90d+

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
A+
DNS Records
4 A records, 97 ms lookup
PASS
4 A records, 97 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 13.227.107.118, 13.227.107.17, 13.227.107.125, 13.227.107.51
Info::
Has 8 IPv6 (AAAA) record(s)
Got: 2600:9000:21ed:1400:8:e1de:4d80:93a1, 2600:9000:21ed:d600:8:e1de:4d80:93a1, 2600:9000:21ed:e200:8:e1de:4d80:93a1, 2600:9000:21ed:200:8:e1de:4d80:93a1, 2600:9000:21ed:ba00:8:e1de:4d80:93a1, 2600:9000:21ed:b400:8:e1de:4d80:93a1, 2600:9000:21ed:e400:8:e1de:4d80:93a1, 2600:9000:21ed:1a00:8:e1de:4d80:93a1
Info::
4 nameserver(s) configured
Got: ns-1049.awsdns-03.org, ns-171.awsdns-21.com, ns-1956.awsdns-52.co.uk, ns-772.awsdns-32.net
Info::
7 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: 97 ms
Got: 97 ms
A13.227.107.118, 13.227.107.17, 13.227.107.125, 13.227.107.51
AAAA2600:9000:21ed:1400:8:e1de:4d80:93a1, 2600:9000:21ed:d600:8:e1de:4d80:93a1, 2600:9000:21ed:e200:8:e1de:4d80:93a1, 2600:9000:21ed:200:8:e1de:4d80:93a1, 2600:9000:21ed:ba00:8:e1de:4d80:93a1, 2600:9000:21ed:b400:8:e1de:4d80:93a1, 2600:9000:21ed:e400:8:e1de:4d80:93a1, 2600:9000:21ed:1a00:8:e1de:4d80:93a1
CNAME—
NSns-1049.awsdns-03.org, ns-171.awsdns-21.com, ns-1956.awsdns-52.co.uk, ns-772.awsdns-32.net
MX
10 aspmx.l.google.com
20 alt1.aspmx.l.google.com
20 alt2.aspmx.l.google.com
30 aspmx5.googlemail.com
30 aspmx4.googlemail.com
30 aspmx2.googlemail.com
30 aspmx3.googlemail.com
TXT
google-site-verification=OCwPip5vYMz3KMtOVXGDy8MVETsPPKp8zcR5gxcP0mk
pardot859913=459e91b4646f79a9dc3bb58970676deab274ab5fb48dbb4a2ae1f01950a469f5
pardot859913=4e67330c615e435955fd1e1973811b368a84de7712bebe791483228997d47650
tollbit-domain-verification=ab1c17a1ab4e8ab035fb8a8604e95a061f65f5fd0528c53a36a7...
SPF v=spf1 include:_spf.google.com include:amazonses.com include:servers.mcsv.net in...
CAALookup not available with standard resolver
Resolved in 97 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://qiita.com

https://qiita.com

1732 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://qiita.com2001732 msHTTP/1.1nginx
A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2600:9000:21ed:1400:8:e1de:4d80:93a1, 2600:9000:21ed:d600:8:e1de:4d80:93a1, 2600:9000:21ed:e200:8:e1de:4d80:93a1, 2600:9000:21ed:200:8:e1de:4d80:93a1, 2600:9000:21ed:ba00:8:e1de:4d80:93a1, 2600:9000:21ed:b400:8:e1de:4d80:93a1, 2600:9000:21ed:e400:8:e1de:4d80:93a1, 2600:9000:21ed:1a00:8:e1de:4d80:93a1
Got: 1 ms connect
IPv6 Ready
AAAA Records 2600:9000:21ed:1400:8:e1de:4d80:93a1, 2600:9000:21ed:d600:8:e1de:4d80:93a1, 2600:9000:21ed:e200:8:e1de:4d80:93a1, 2600:9000:21ed:200:8:e1de:4d80:93a1, 2600:9000:21ed:ba00:8:e1de:4d80:93a1, 2600:9000:21ed:b400:8:e1de:4d80:93a1, 2600:9000:21ed:e400:8:e1de:4d80:93a1, 2600:9000:21ed:1a00:8:e1de:4d80:93a1 Connection Reachable (1 ms)
A+
Crawlability
robots.txt present, sitemap with 27 URLs
PASS
robots.txt present, sitemap with 27 URLs
Info::
robots.txt is present
Got: 380 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 27 entries
Info::
Sitemap index with 27 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 380 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
# See http://www.robotstxt.org/wc/norobots.html for documentation on how to use the robots.txt file
User-agent: *
Disallow: /*/edit$
Disallow: /api/*
Disallow: /graphql$
Disallow: /policies/td-optout$
Disallow: /search
Disallow: *.md
Disallow: */items/*/revisions
Disallow: */private/*/revisions
Allow:    /api/*/docs$

Sitemap: https://cdn.qiita.com/sitemap-https/sitemap.xml.gz
sitemap.xml 200 OK
Type Sitemap Index URLs 27 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

503https://www.qiita.com/
200https://qiita.com/

HTTP → HTTPS

301http://qiita.com/ → https://qiita.com/

Consistent

A
Domain Intelligence
qiita.com — via Amazon Registrar, Inc., 14 years, 11 months old
PASS
qiita.com — via Amazon Registrar, Inc., 14 years, 11 months old
Warning::
Domain expires in 87 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 18, 2026
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: Amazon Registrar, 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.
Domain expiry

Expires today

July 18, 2026

SSL certificate

163 days

Issued by Amazon

Domain age

14 years, 11 months

Registered July 18, 2011

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2600:9000:21ed:f400:8:e1de:4d80:93a1

Registrar

Amazon Registrar, Inc.

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 Amazon Registrar, Inc.
Created July 18, 2011 (14 years, 11 months ago)
Expires July 18, 2026 (2 months)
Last Updated June 13, 2025
Name Servers ns-1049.awsdns-03.org, ns-171.awsdns-21.com, ns-1956.awsdns-52.co.uk, ns-772.awsdns-32.net
DNSSEC Not enabled
Hosting
IP Address 2600:9000:21ed:f400:8:e1de:4d80:93a1
Data source: rdap (0.4s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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
CDN & Delivery
AWS CloudFront (Miss from cloudfront)
PASS
AWS CloudFront (Miss from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: GRU3-P11)
Got: x-amz-cf-id: nGzCmYSb1wTyGuJ4pAzPi4ywlCebu6CzGNBA80EpqFeCNjuNZYBPhw==
Info::
CDN cache status: Miss from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Miss from cloudfront Evidence x-amz-cf-id: nGzCmYSb1wTyGuJ4pAzPi4ywlCebu6CzGNBA80EpqFeCNjuNZYBPhw==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback