Skip to content
https://chineseface.app

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
10
PASS
7
INFO
0
Probed from Sao Paulo, Brazil
200 OK
Checks
17
7 PASS 10 REVIEW
B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 172.67.201.62: lookup 172.67.201.62: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 104.21.76.212: lookup 104.21.76.212: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3031::6815:4cd4: lookup 2606:4700:3031::6815:4cd4: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2606:4700:3036::ac43:c93e: lookup 2606:4700:3036::ac43:c93e: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
Multi-Resolver DNS Speed
Mean 75ms across 3 resolvers (spread 154ms)
REVIEW
Mean 75ms across 3 resolvers (spread 154ms)
Info::
Cloudflare: 4ms
Got: 4ms via 1.1.1.1:53
Info::
Google: 65ms
Got: 65ms via 8.8.8.8:53
Info::
Quad9: 158ms
Got: 158ms via 9.9.9.9:53
C
HTTP Probe Timing
Action
Total 1795 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
117 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.
10 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
1.76 s
Total Time Total request time from DNS lookup through full response.
1.80 s

Connection waterfall

DNS Lookup 117 ms TCP Connect 2 ms TLS Handshake 10 ms Server Processing 1.63 s Content Transfer 34 ms
B
TLS Certificate Expiry & Recommendations
88 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

88
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
Cloudflare
REVIEW
Cloudflare
Info::
Document is served via Cloudflare CDN (edge: GRU)
Got: cf-ray: a4c1a108c9e8f1c5-GRU
Document served via CDN: Cloudflare
Provider Cloudflare Evidence cf-ray: a4c1a108c9e8f1c5-GRU
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
B
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
DNS Records
2 A records, 126 ms lookup
PASS
2 A records, 126 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.67.201.62, 104.21.76.212
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:3031::6815:4cd4, 2606:4700:3036::ac43:c93e
Info::
2 nameserver(s) configured
Got: andronicus.ns.cloudflare.com, isabel.ns.cloudflare.com
Info::
3 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 126 ms
Got: 126 ms
A172.67.201.62, 104.21.76.212
AAAA2606:4700:3031::6815:4cd4, 2606:4700:3036::ac43:c93e
CNAME—
NSandronicus.ns.cloudflare.com, isabel.ns.cloudflare.com
MX
57 route1.mx.cloudflare.net
84 route2.mx.cloudflare.net
93 route3.mx.cloudflare.net
TXT
SPF v=spf1 include:_spf.mx.cloudflare.net ~all
CAALookup not available with standard resolver
Resolved in 126 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://chineseface.app

https://chineseface.app

733 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://chineseface.app200733 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:3031::6815:4cd4, 2606:4700:3036::ac43:c93e
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:3031::6815:4cd4, 2606:4700:3036::ac43:c93e Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 314 URLs
PASS
robots.txt present, sitemap with 314 URLs
Info::
robots.txt is present
Got: 271 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 314 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 271 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-Agent: *
Allow: /
Disallow: /api/
Disallow: /settings/
Disallow: /dashboard/
Disallow: /auth/
Disallow: /admin/
Disallow: /payment/
Disallow: /reading/

Host: chineseface.app
Sitemap: https://chineseface.app/sitemap.xml
# LLM brief: https://chineseface.app/llms.txt
sitemap.xml 200 OK
Type URL Set URLs 314 entries Valid XML Yes
Sample URLs:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

301https://www.chineseface.app/
200https://chineseface.app/

Preferred variant: non-www

HTTP → HTTPS

301http://chineseface.app/ → https://chineseface.app/

Consistent

A+
Domain Intelligence
chineseface.app — via Namecheap Inc., 1 days old
PASS
chineseface.app — via Namecheap Inc., 1 days old
Info::
Domain registered until Oct 16, 2027 (1 years remaining)
Info::
Domain is only 1 days old
Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.
Got: Registered Oct 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: Namecheap 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

362 days

October 16, 2027

SSL certificate

88 days

Issued by Google Trust Services

Domain age

1 days

Registered October 16, 2026

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:3036::ac43:c93e

Registrar

Namecheap Inc.

Unlocked 2 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
  • Newly registered domain — build backlinks and content to establish SEO trust
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Namecheap Inc.
Created October 16, 2026 (1 days ago)
Expires October 16, 2027 (1 years)
Last Updated October 16, 2026
Name Servers andronicus.ns.cloudflare.com, isabel.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:3036::ac43:c93e
Data source: rdap (0.5s)

Newly registered domains may face SEO trust challenges. Search engines generally give more authority to older domains. This is informational — not a problem to fix.

Why this matters

Informational: domain age. Newer domains may have lower trust signals in spam/security filters.

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