Skip to content
https://pixiv.net

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
79
GRADE
C
FIX
1
REVIEW
6
PASS
2
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
2 PASS 6 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.

B
Redirect Chain
1 redirect(s), 1385 ms total
REVIEW
1 redirect(s), 1385 ms total
Info::
Single redirect
Got: https://pixiv.net → https://www.pixiv.net/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1385 ms total
Got: 1385 ms

https://pixiv.net

1037 ms · HTTP/1.1

301

https://www.pixiv.net/

348 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://pixiv.net3011037 msHTTP/1.1nginx
2https://www.pixiv.net/200348 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

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
robots.txt present, no sitemap
REVIEW
robots.txt present, no sitemap
Info::
robots.txt is present
Got: 1032 bytes
Info::
No sitemap.xml found
A sitemap helps search engines discover and index your pages more efficiently.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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

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 1032 B Sitemaps referenced 0 User-agents omgilibot, GPTBot, Applebot-Extended, meta-externalagent, cohere-ai, CCBot, omgili, Diffbot, *, Google-Extended, anthropic-ai, ClaudeBot, FacebookBot Blocking No — crawling allowed
User-agent: *
Disallow: /cdn-cgi/
Disallow: /rpc/index.php?mode=profile_module_illusts&user_id=*&illust_id=*
Disallow: /ajax/illust/*/recommend/init
Disallow: *return_to*
Disallow: /?return_to=
Disallow: /login.php?return_to=
Disallow: /index.php?return_to=

Disallow: /artworks/unlisted/*

Disallow: /users/*/followers
Disallow: /users/*/mypixiv
Disallow: /users/*/bookmarks
Disallow: /novel/comments.php?id=
Disallow: /novels/unlisted/*

Disallow: /en/group

Disallow: /en/search/

Disallow: /en/users/*/followers
Disallow: /en/users/*/mypixiv
Disallow: /en/users/*/bookmarks
Disallow: /en/novel/comments.php?id=

Disallow: /fanbox/search
Disallow: /fanbox/tag

Allow: /comic-indies/$
Allow: /comic-indies/about
Disallow: /comic-indies/

User-Agent: GPTBot
User-Agent: Google-Extended
User-Agent: anthropic-ai
User-Agent: ClaudeBot
User-Agent: FacebookBot
User-Agent: Applebot-Extended
User-Agent: meta-externalagent
User-Agent: cohere-ai
User-Agent: CCBot
User-Agent: omgili
User-Agent: Diffbot
User-Agent: omgilibot
Disallow: /

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::
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.pixiv.net/
200https://pixiv.net/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://pixiv.net/ https://www.pixiv.net/

Consistent

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

Connection waterfall

DNS Lookup 33 ms TCP Connect 259 ms TLS Handshake 523 ms Server Processing 259 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
73 days until leaf cert expires — 5 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Prefer TLS 1.3 — TLS 1.2 is acceptable but TLS 1.3 removes RSA key exchange and improves latency
  • 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, 40 ms lookup
PASS
4 A records, 40 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 210.140.139.161, 210.140.139.158, 210.140.139.155, 210.140.139.152
Info::
No IPv6 (AAAA) records
Info::
2 nameserver(s) configured
Got: ns2.pixiv.net, ns1.pixiv.net
Info::
5 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: 40 ms
Got: 40 ms
A210.140.139.161, 210.140.139.158, 210.140.139.155, 210.140.139.152
AAAA
CNAME
NSns2.pixiv.net, ns1.pixiv.net
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 alt3.aspmx.l.google.com
10 alt4.aspmx.l.google.com
TXT
google-site-verification=eVfT24dAtKUSNJTkjJKoEr4LOBLJyLfm3YN59oP5bRE
SPF v=spf1 include:_spf.pixiv.net include:mail.zendesk.com include:sendgrid.net incl...
firebase=pixiv-comic-store-production
google-site-verification=xAnUeXKY_KgBIU3bipOPWHY9svivd1TqrjcW78IbVoI
ca3-9373f91b0f6c49ee984a67d1e6325e4f
google-site-verification=oxtVRjNBArcXLAcQAnu4cMCqNrHIdNjRLdGE9yOsXOo
globalsign-domain-verification=e_Nj1kv39zKi39YDMjczo6I7enPLWRCo7nMfs7uXGW
google-site-verification=vNUz01aVidCrTTtKNCaiqUlfjOxCmVHRiuRQLTRq63A
OSSRH-78583
facebook-domain-verification=ehppa9dvc6xcigimqv0ydnvdzl0kml
google-site-verification=rS1Mg2WHOuRkdwyS88Gfbm-Ol465if5TTLUL5h9lu-E
CAALookup not available with standard resolver
Resolved in 40 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
Domain Intelligence
pixiv.net — via Key-Systems GmbH, 19 years old, hosted on IDCF IDC Frontier Inc., JP
PASS
pixiv.net — via Key-Systems GmbH, 19 years old, hosted on IDCF IDC Frontier Inc., JP
Warning::
Domain expires in 85 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 16, 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: Key-Systems 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: IDCF IDC Frontier Inc., JP
Got: AS4694
Domain expiry

EXPIRED

July 16, 2026

SSL certificate

73 days

Issued by Google Trust Services

Domain age

19 years

Registered July 16, 2007

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

IDCF IDC Frontier Inc., JP

ASN AS4694

210.140.139.161

Registrar

Key-Systems GmbH

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Key-Systems GmbH
Created July 16, 2007 (19 years ago)
Expires July 16, 2026 (2 months)
Last Updated November 30, 2025
Name Servers ns1.pixiv.net, ns2.pixiv.net
DNSSEC Not enabled
Hosting
IP Address 210.140.139.161
ASN AS4694 (IDCF IDC Frontier Inc., JP)
Provider IDCF IDC Frontier Inc., JP
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

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

Send Feedback