Skip to main content

Security report for eas.org

Eastern Analytical Symposium · Education · N/a

Critical risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

25/100

Risk levelCritical

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

The Eastern Analytical Symposium website serves as an informational platform for a non-profit organization dedicated to the analytical chemistry community. It provides details about symposium events, awards, exhibitor information, and educational opportunities. The site targets professionals, researchers, exhibitors, and students interested in analytical chemistry. The business model revolves around hosting annual symposiums, exhibitions, and educational short courses, supported by sponsorships and exhibitor participation. The website demonstrates consistent branding and good content relevance, with a professional design and clear navigation structure. Technically, the site is built on WordPress 6.6.2 with several plugins including Yoast SEO and Kadence Blocks, hosted on a LiteSpeed server. While the site is mobile-optimized and SEO-friendly, performance metrics are unavailable, and some accessibility features are basic. The absence of a valid SSL certificate and HTTPS support is a critical security shortfall, limiting secure user interactions and trust. From a security perspective, the site lacks HTTPS, modern TLS protocols, and essential security headers. No privacy or cookie policies are present, and no direct contact information such as emails or phone numbers are provided, which impacts privacy compliance and user trust. Analytics usage is minimal, relying on StatCounter, with no evident advanced tracking or retargeting. Overall, the site is functional and informative but requires urgent improvements in security, privacy compliance, and contact transparency to enhance trustworthiness and protect user data. Strategic recommendations include implementing HTTPS, publishing privacy and cookie policies, and providing clear contact details to improve compliance and user confidence.

Scanned

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
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

9 findings rated critical or high. Fix these first.

  1. GDPR outside view

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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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 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';…

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

Keep watching eas.org

This scan found 17 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. The full timeline opens with your unlock code.

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
0
Security headers
15
Email security
50
DNS health
50
Network security
20
GDPR outside view
15
Average
25

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

The Eastern Analytical Symposium holds a strong position within the analytical chemistry education and event sector, focusing on community engagement through symposiums, awards, and educational programs. Its non-profit status and specialized target audience suggest a niche market with stable demand. The business model leverages event sponsorships, exhibitor fees, and educational offerings. The website content and structure support this model effectively, though the lack of direct contact details and privacy policies may hinder broader engagement and partnership opportunities. The organization appears to maintain consistent branding and professional content, which supports its reputation in the sector. Growth potential exists through enhanced digital presence and improved security and privacy practices.

Security posture

The website's security posture is weak due to the absence of HTTPS and a valid SSL certificate, exposing users to potential data interception risks. No modern TLS protocols are enabled, and critical security headers are missing. The site does not implement HSTS, OCSP stapling, or session resumption, which are standard best practices for secure web operations. No vulnerability disclosure or incident response information is provided, indicating limited readiness for security incidents. The lack of privacy and cookie policies further exposes compliance risks, particularly under GDPR or similar regulations. Overall, the site requires immediate security enhancements to protect user data and improve trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Publish comprehensive privacy and cookie policies to comply with GDPR and inform users.
  3. Add direct contact information including verified company emails and phone numbers for transparency.
  4. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Enable HSTS with includeSubDomains and preload options, and configure OCSP stapling and session resumption.
  6. Consider adding a security.txt file and vulnerability disclosure policy to improve security transparency.
  7. Improve accessibility features and provide clear cookie consent mechanisms.
  8. Enhance analytics transparency and data retention policies to align with privacy best practices.
Technical notes

Notes

The website is built on a modern WordPress platform with up-to-date plugins such as Yoast SEO and Kadence Blocks, indicating a maintained CMS environment. Hosting on a LiteSpeed server suggests good server performance potential, though actual performance data is missing. The site uses jQuery and several WordPress core scripts, with structured data implemented via JSON-LD for SEO benefits. However, the lack of HTTPS and modern TLS protocols is a significant technical deficiency. The site is mobile-optimized and SEO-friendly but could benefit from improved accessibility and performance monitoring. Technical debt appears moderate, with opportunities for modernization in security and privacy implementations.
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 eas.org. 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 eas.org.

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.