Security Report Summary
D
| Site: | https://www.xiaopeng.com/ | ||
|---|---|---|---|
| IP Address: | 163.181.253.199 | ||
| Report Time: | 29 Oct 2026 03:54:15 UTC | ||
| Headers: |
|
||
| Advanced: |
|
Missing Headers
| Content-Security-Policy | Content Security Policy is an effective measure to protect your site from XSS attacks. By whitelisting sources of approved content, you can prevent the browser from loading malicious assets. |
|---|---|
| X-Frame-Options | X-Frame-Options tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. Recommended value "X-Frame-Options: SAMEORIGIN". |
| X-Content-Type-Options | X-Content-Type-Options stops a browser from trying to MIME-sniff the content type and forces it to stick with the declared content-type. The only valid value for this header is "X-Content-Type-Options: nosniff". |
| Referrer-Policy | Referrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites. |
| Permissions-Policy | Permissions Policy is a new header that allows a site to control which features and APIs can be used in the browser. |
Raw Headers
| HTTP/2 | 200 |
|---|---|
| server | Tengine |
| content-type | text/html; charset=utf-8 |
| date | Thu, 29 Oct 2026 03:54:14 GMT |
| set-cookie | acw_tc=781bad1c17932460545895733eb24530b1591049755fa2d263f09ad627b443;path=/;HttpOnly;Max-Age=1800 |
| x-powered-by | Next.js |
| set-cookie | deviceId=5cac1.34fb0922c_1793246054644; Max-Age=2592000; Path=/; Expires=Sat, 28 Nov 2026 03:54:14 GMT |
| vary | rsc, next-router-state-tree, next-router-prefetch, next-router-segment-prefetch, Accept-Encoding |
| link | <https://xps01.xiaopeng.com/domestic/_next/static/chunks/012d22e9b44a6683.css>; rel=preload; as="style", <https://xps01.xiaopeng.com/domestic/_next/static/chunks/6cbb6e31566e3f08.css>; rel=preload; as="style", <https://xps01.xiaopeng.com/domestic/_next/static/chunks/7e53d0ee997d118a.css>; rel=preload; as="style", <https://xps01.xiaopeng.com/domestic/_next/static/chunks/de4ed038530d8c6f.css>; rel=preload; as="style", <https://xps01.xiaopeng.com/domestic/_next/static/chunks/d59b15bccc06d438.css>; rel=preload; as="style", <https://xps01.xiaopeng.com/domestic/_next/static/chunks/43fe1e93acd3b1b3.css>; rel=preload; as="style", <https://xps01.xiaopeng.com/domestic/_next/static/chunks/d0df0a9d861f7bf1.css>; rel=preload; as="style" |
| cache-control | private, no-cache, no-store, max-age=0, must-revalidate |
| content-encoding | gzip |
| access-control-allow-origin | * |
| allow | GET, POST, HEAD, OPTIONS |
| strict-transport-security | max-age=31536000 |
| via | cache42.l2ea120-5[124,0], cache42.l2ea120-5[125,0], ens-cache21.fr6[755,0] |
| timing-allow-origin | * |
| eagleid | a3b5fda917932460540292910e |
Upcoming Headers
| Cross-Origin-Embedder-Policy | Cross-Origin Embedder Policy allows a site to prevent assets being loaded that do not grant permission to load them via CORS or CORP. |
|---|---|
| Cross-Origin-Opener-Policy | Cross-Origin Opener Policy allows a site to opt-in to Cross-Origin Isolation in the browser. |
| Cross-Origin-Resource-Policy | Cross-Origin Resource Policy allows a resource owner to specify who can load the resource. |
Additional Information
| server | Server value has been changed. Typically you will see values like "Microsoft-IIS/8.0" or "nginx 1.7.2". |
|---|---|
| x-powered-by | X-Powered-By can usually be seen with values like "PHP/5.5.9-1ubuntu4.5" or "ASP.NET". Trying to minimise the amount of information you give out about your server is a good idea. This header seems to have been altered to remove such information, but could still be removed. |
| access-control-allow-origin | This is a very lax CORS policy. Such a policy should only be used on a public CDN. |
| strict-transport-security | HTTP Strict Transport Security is an excellent feature to support on your site and strengthens your implementation of TLS by getting the User Agent to enforce the use of HTTPS. |