Skip to content
https://iqiyi.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
1
REVIEW
4
PASS
4
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
4 PASS 4 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), 1909 ms total
REVIEW
1 redirect(s), 1909 ms total
Info::
Single redirect
Got: https://iqiyi.com → https://www.iqiyi.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1909 ms total
Got: 1909 ms

https://iqiyi.com

1005 ms · HTTP/1.1

301

https://www.iqiyi.com/

904 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://iqiyi.com3011005 msHTTP/1.1QWS
2https://www.iqiyi.com/200904 msHTTP/1.1QWS

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.iqiyi.com/
200https://iqiyi.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://iqiyi.com/ → https://www.iqiyi.com/

Consistent

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

Connection waterfall

DNS Lookup 259 ms TCP Connect 261 ms TLS Handshake 265 ms Server Processing 262 ms Content Transfer 0 ms
B
TLS Certificate Expiry & Recommendations
112 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

112
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
7 A records, 269 ms lookup
PASS
7 A records, 269 ms lookup
Info::
Resolves to 7 IPv4 address(es)
Got: 202.108.14.125, 110.242.75.43, 202.108.14.124, 110.242.75.41, 110.242.75.42, 110.242.75.40, 202.108.14.130
Info::
Has 7 IPv6 (AAAA) record(s)
Got: 2408:871a:2100:2fff:1000::4, 2408:8706:0:4997::12, 2408:8706:0:4997::13, 2408:8706:0:4997::11, 2408:871a:2100:2fff:1000::7, 2408:871a:2100:2fff:1000::6, 2408:871a:2100:2fff:1000::5
Info::
4 nameserver(s) configured
Got: ns1.iqiyi.com, ns2.iqiyi.com, ns3.iqiyi.com, ns4.iqiyi.com
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 (269 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 269 ms
A202.108.14.125, 110.242.75.43, 202.108.14.124, 110.242.75.41, 110.242.75.42, 110.242.75.40, 202.108.14.130
AAAA2408:871a:2100:2fff:1000::4, 2408:8706:0:4997::12, 2408:8706:0:4997::13, 2408:8706:0:4997::11, 2408:871a:2100:2fff:1000::7, 2408:871a:2100:2fff:1000::6, 2408:871a:2100:2fff:1000::5
CNAME—
NSns1.iqiyi.com, ns2.iqiyi.com, ns3.iqiyi.com, ns4.iqiyi.com
MX
10 mx1.iqiyi.com
TXT
SPF v=spf1 ip4:202.108.14.131 ip4:116.211.199.239 ip4:129.227.142.193 ip4:23.236.118...
_xsvedivdugs9dmgt7tewxt6q327cmym
CAALookup not available with standard resolver
Resolved in 269 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 (249 ms)
PASS
IPv6 reachable (249 ms)
Info::
IPv6 is configured and reachable at 2408:871a:2100:2fff:1000::4, 2408:8706:0:4997::12, 2408:8706:0:4997::13, 2408:8706:0:4997::11, 2408:871a:2100:2fff:1000::7, 2408:871a:2100:2fff:1000::6, 2408:871a:2100:2fff:1000::5
Got: 249 ms connect
IPv6 Ready
AAAA Records 2408:871a:2100:2fff:1000::4, 2408:8706:0:4997::12, 2408:8706:0:4997::13, 2408:8706:0:4997::11, 2408:871a:2100:2fff:1000::7, 2408:871a:2100:2fff:1000::6, 2408:871a:2100:2fff:1000::5 Connection Reachable (249 ms)
A+
Crawlability
robots.txt present, sitemap with 12 URLs
PASS
robots.txt present, sitemap with 12 URLs
Info::
robots.txt is present
Got: 697 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 12 entries
Info::
Sitemap index with 12 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 697 B Sitemaps referenced 1 User-agents *, openai, gptbot, OAl-SearchBot, claudebot, pangubot, petalbot, ChatGLM-Spider, omigili, chatgpt-user, ChatGLMBot, skyworkspider, perplexitybot, cohere-ai Blocking No — crawling allowed
User-agent: openai

Disallow: /


User-agent: gptbot

Disallow: /


User-agent: chatgpt-user

Disallow: /


User-agent: OAl-SearchBot

Disallow: /


User-agent: claudebot

Disallow: /


User-agent: pangubot

Disallow: /


User-agent: petalbot

Disallow: /


User-agent: ChatGLM-Spider

Disallow: /


User-agent: ChatGLMBot

Disallow: /


User-agent: skyworkspider

Disallow: /


User-agent: perplexitybot

Disallow: /


User-agent: omigili

Disallow: /


User-agent: cohere-ai

Disallow: /


User-agent: *

Disallow: /lib/pps/

Disallow: /lib/iqy/

Disallow: /lib/pstyle/

Disallow: /lib/lstyle/

Disallow: /lib/mac/

#Disallow: /test123/


Sitemap: https://www.iqiyi.com/sitemap.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 12 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
iqiyi.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 16 years old
PASS
iqiyi.com — via Alibaba Cloud Computing (Beijing) Co., Ltd., 16 years old
Info::
Domain registered until Jul 11, 2029 (3 years, 3 months remaining)
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: Alibaba Cloud Computing (Beijing) Co., Ltd.
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

1092 days

July 11, 2029

SSL certificate

112 days

Issued by GlobalSign nv-sa

Domain age

16 years

Registered July 11, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2408:8706:0:4997::11

Registrar

Alibaba Cloud Computing (Beijing) Co., Ltd.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Alibaba Cloud Computing (Beijing) Co., Ltd.
Created July 11, 2010 (16 years ago)
Expires July 11, 2029 (3 years, 3 months)
Last Updated September 29, 2025
Name Servers ns1.iqiyi.com, ns2.iqiyi.com, ns3.iqiyi.com, ns4.iqiyi.com
DNSSEC Not enabled
Hosting
IP Address 2408:8706:0:4997::11
Data source: rdap (0.1s)

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