Skip to main content

Security report for who.cx

Technology · China

Medium risk. 7 critical or high findings in Email security, Security headers and 2 other checks.

Security score

68/100

Risk levelMedium

0–100, higher is better. How it is calculated

WHO.CX is a specialized web-based service providing comprehensive whois lookup capabilities supporting over 2000 domain suffixes. The platform targets domain registrants, webmasters, and IT professionals primarily in China, offering detailed domain registration, pricing, renewal, and DNS information. The website is relatively new, founded in 2022, and operates with a focused niche in the domain information services market. The business model revolves around providing free and enhanced whois query tools with optional donation support. Technically, the website employs standard modern web technologies including HTML5, CSS3, JavaScript, and SVG graphics. It uses asynchronous script loading and local storage for user preferences, supporting multiple languages and time zones. The site performance is moderate with good mobile optimization and basic accessibility features. However, no CMS or advanced frameworks are detected, indicating a lightweight custom implementation. From a security perspective, the domain registration is transparent and consistent with the website's purpose, with clientTransferProhibited status adding trust. However, DNSSEC is not enabled, and no explicit security headers are present in the HTML content, which are areas for improvement. The site uses HTTPS (implied by external script loading over HTTPS), but no explicit security or privacy policies are published. Analytics are conducted via 51.la, with moderate user tracking but no cookie consent mechanism. Overall, WHO.CX presents a functional and niche-focused service with moderate technical maturity and business credibility. Security posture and privacy compliance require enhancements to meet higher standards. Strategic recommendations include enabling DNSSEC, implementing security headers, publishing privacy and cookie policies, and improving incident response transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

7 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching who.cx

This scan found 21 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
75
Security headers
50
Email security
60
DNS health
70
Network security
100
GDPR outside view
50
Average
68

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention who.cx, from OffSeq Breach.

No leaked records found

Breach holds no records for who.cx right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

WHO.CX operates in the technology sector as a domain whois lookup service provider. It holds a niche market position catering to domain registrants and webmasters needing detailed domain registration and DNS information. The business model appears to be service-oriented with optional donations as a revenue stream. The company is small-sized, founded recently in 2022, and primarily serves the Chinese market with multilingual support. Competitive advantages include support for over 2000 domain suffixes and integrated pricing and renewal data. The partnership ecosystem is minimal with no explicit partners or subsidiaries identified. Growth indicators are limited due to the site's recent launch and lack of extensive business disclosures.

Security posture

The security maturity of WHO.CX is moderate. The domain registration is transparent and consistent, with clientTransferProhibited status enhancing domain security. However, the absence of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security reduces the overall security posture. No privacy or incident response policies are published, indicating gaps in compliance and readiness. The use of 51.la analytics introduces moderate user tracking without explicit consent mechanisms. No critical vulnerabilities or malware indicators were detected. The site would benefit from adopting standard security best practices and enhancing transparency to improve trust and compliance.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and integrity.
  2. Implement essential security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  4. Establish and disclose incident response procedures and security contact channels.
  5. Review and minimize user tracking practices and implement cookie consent mechanisms.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
追求极致的whois查询。支持2000+后缀，同时支持价格、备案和IANA查询，提炼有效数据，时区自动转换，国别城市自动转中文，域名重要状态提示
Key services
whois queries, domain registration info, price and renewal info, DNS queries, time zone and currency conversion
Content quality
good
Branding
moderate

Technology

Stack
HTML5, CSS3, JavaScript, localStorage, SVG, async JavaScript loading
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
50/100
Good practices seen
  • clientTransferProhibited domain status

Analytics and tracking

Services
51.la
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
sdk.51.la
Marketing tools
51.la analytics
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is a specialized whois lookup tool supporting 2000+ domain suffixes
  2. Content is primarily in Simplified Chinese with multi-language support
  3. No privacy or cookie policies found
  4. Contact email found in donation modal footer
  5. No phone numbers or physical addresses found
  6. No security or incident response policies published
  7. Uses 51.la analytics for tracking
  8. No explicit security headers detected
  9. No WAF or blocking mechanisms detected
  10. Domain registration is recent but consistent with business
Technical notes

Notes

WHO.CX is built using standard web technologies with a lightweight custom implementation. The site uses HTML5, CSS3, JavaScript, and SVG for UI elements, with asynchronous script loading for analytics. It supports multiple languages and time zones, enhancing user experience. Hosting details are not explicit but the registrar is a Chinese entity. Performance is moderate with good mobile optimization but basic accessibility features. No CMS or major frameworks are detected, indicating low technical debt but also limited scalability features. Security technical gaps include missing DNSSEC and security headers. Overall, the technical infrastructure is adequate for the site's scope but can be improved for security and compliance.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with who.cx. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review who.cx.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.