Skip to main content

Security report for whmxyj.com

Other · N/a

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

Security score

63/100

Risk levelMedium

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

The website at whmxyj.com is currently non-functional with an empty HTML body and no visible content, metadata, or business information. The domain WHOIS data is suspicious, showing a creation date in the future (March 19, 2025), which undermines the legitimacy and trustworthiness of the domain. No contact details, privacy policies, or security measures are present, indicating a lack of operational maturity or possibly a placeholder or abandoned domain. The absence of any technical or business content prevents meaningful analysis of the company's market position or services. From a technical perspective, the site lacks any detectable technology stack, frameworks, or CMS. No security headers or HTTPS information were provided, and DNSSEC is not enabled, which are basic security best practices. The website shows poor performance indicators due to the absence of content and optimization. No analytics or advertising technologies are detected, and no user tracking or privacy compliance mechanisms are in place. Security posture is weak due to the lack of visible security controls, policies, or incident response channels. The suspicious WHOIS data further reduces trust and raises concerns about the domain's legitimacy. Overall, the site presents a high risk due to its lack of transparency, content, and security measures. Strategically, this domain should be treated with caution. Without further information or content, it cannot be considered a credible or trustworthy business website. It is recommended to monitor the domain for future updates or changes that may clarify its purpose and legitimacy.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 whmxyj.com

This scan found 25 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
72
Security headers
30
Email security
60
DNS health
75
Network security
100
GDPR outside view
40
Average
63

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

Technical appendix

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

Business context

Business profile

No business intelligence data could be extracted due to the absence of content, metadata, or structured data on the website. The domain WHOIS data is inconsistent and suspicious, providing no registrant organization or contact details. There is no indication of market positioning, business model, revenue streams, or partnerships. The lack of any business-related information suggests the domain is either inactive, a placeholder, or potentially fraudulent.

Security posture

The security posture of the website is poor. No security headers or HTTPS information were provided, and DNSSEC is not enabled. There are no visible security policies, incident response contacts, or vulnerability disclosures. The suspicious WHOIS data with a future creation date further undermines trust. No forms or data collection mechanisms are present to assess input security. Overall, the site lacks basic security hygiene and transparency, posing potential risks if activated without proper controls.

Recommendations

  1. Enable and configure DNSSEC to improve domain name system security.
  2. Implement HTTPS with a valid SSL certificate to secure communications.
  3. Add comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  4. Publish clear contact information and incident response channels to enhance transparency and trust.
  5. Conduct a full website content and security audit before launching any services to ensure compliance and security best practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
inconsistent

Technology

Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

Security

Observed score
30/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
poor
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is completely empty with no metadata, no text, no images, no scripts.
  2. No contact information or business details present on the site.
  3. No privacy, cookie, or terms of service policies found.
  4. No security headers or HTTPS information available from provided data.
  5. WHOIS data is suspicious with future creation date and minimal details.
  6. No external links or social media references found.
  7. No forms or data collection mechanisms present.
  8. No analytics or advertising technologies detected.
  9. Website appears inactive or placeholder with no meaningful content.
Technical notes

Notes

The website currently consists of an empty HTML document with no metadata, scripts, or content. No technologies, frameworks, or CMS platforms are detected. DNSSEC is not enabled, and the WHOIS data is suspicious with a future creation date. Hosting provider information is not available. Performance and mobile optimization cannot be assessed due to lack of content. The site lacks SEO and accessibility features. Overall, the technical infrastructure appears minimal or non-existent, indicating a placeholder or inactive domain.
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 whmxyj.com. 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 whmxyj.com.

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.