Skip to main content

Security report for iem.com

IEM · Government · United States

Medium risk. 5 critical or high findings in SSL/TLS, Security headers and 1 other check.

Security score

63/100

Risk levelMedium

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

IEM is a well-established company specializing in emergency management, disaster recovery, and resilience services primarily for government and public sector clients. With over 40 years of experience, IEM offers a broad range of capabilities including digital citizen services, public health modeling, energy security planning, and law enforcement support. The company positions itself as a trusted partner to governments and businesses worldwide, aiming to build a safer and more resilient world. The website reflects this positioning with comprehensive service descriptions and a professional digital presence. Technically, the website is built on WordPress using the Themify Ultra theme and incorporates multiple plugins for enhanced functionality such as sliders, forms, cookie consent, and analytics. The site is mobile optimized and employs modern web technologies including Google Analytics and Tag Manager for tracking and performance insights. SEO practices are evident through structured data and meta tags, contributing to good search engine visibility. From a security perspective, the site uses HTTPS and has domain transfer protections in place. However, it lacks visible security headers and does not publish a security policy or vulnerability disclosure, which are areas for improvement. The cookie consent mechanism is robust, offering users detailed control over cookie categories, aligning with GDPR requirements. No critical vulnerabilities or blocking mechanisms were detected, indicating a stable security posture. Overall, IEM's website demonstrates a mature digital infrastructure supporting its business goals, with room to enhance privacy and security transparency. Strategic recommendations include publishing a privacy policy, implementing security headers, and establishing a vulnerability disclosure process to further strengthen trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
65/ 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

5 findings rated critical or high. Fix these first.

  1. 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

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

  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 Cookie Policy found

      GDPR requires clear information about cookie usage

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching iem.com

This scan found 18 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
45
Email security
85
DNS health
80
Network security
100
GDPR outside view
65
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

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 iem.com, from OffSeq Breach.

Total records
261
Employees
0
Customers
233
Third parties
28
Weak passwords
41%

3 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for iem.com.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

IEM operates in the government and public sector emergency management market, leveraging decades of experience to deliver specialized services in disaster recovery, resilience, and digital citizen engagement. Its business model focuses on B2G and B2B contracts, providing consulting, software solutions, and operational support. The company’s competitive advantage lies in its comprehensive service portfolio and established reputation. Revenue streams likely include government contracts, grants management, and software licensing. Target customers are federal, state, local, tribal, and territorial governments, as well as private sector partners in energy and defense. The company maintains a strong partnership ecosystem, including regional subsidiaries such as IEM Puerto Rico. Growth indicators include a 40-year legacy and active digital presence. The website content and structure support a professional image aligned with its market position.

Security posture

IEM’s security posture is solid with mandatory HTTPS and domain transfer lock status, reducing risks of interception and unauthorized domain changes. The presence of a cookie consent mechanism with detailed categories indicates awareness of privacy compliance. However, the absence of security headers like CSP, HSTS, and X-Frame-Options, as well as no published security or incident response policies, suggests gaps in defense-in-depth and transparency. No vulnerability disclosure or security.txt file was found, limiting external security collaboration. No exposed sensitive data or vulnerable libraries were detected in the provided content. Overall, the security maturity is moderate to good but can be improved by adopting additional best practices and transparency measures.

Recommendations

  1. Publish a comprehensive privacy policy page linked prominently on the website.
  2. Implement and verify HTTP security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options.
  3. Create and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
  4. Enable DNSSEC for the domain to enhance DNS security and prevent spoofing.
  5. Provide clear contact information including company emails and physical addresses to improve trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
IEM
Description
IEM partners with governments and businesses worldwide to enhance resilience, disaster preparedness, response, and recovery for a safer, stronger future.
Key services
Digital Citizen Services, Disaster Recovery, Emergency Management, Resilience & Mitigation, Energy & Resilience, Public Health Modeling, Law Enforcement Services, Grants Management
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.8.1, Themify Ultra theme, jQuery, Google Analytics, Google Tag Manager, Ninja Forms, Cookie Law Info plugin, Builder Slider Pro, Builder Image Pro, WP Carousel Pro, Simple Membership, Aurora Heatmap
Frameworks
WordPress CMS
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • ClientTransferProhibited domain status to prevent unauthorized transfers
  • Cookie consent banner with detailed categories and user control

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Call Tracking (gstatic.com call-tracking script)
Transparency
basic

Site quality

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

Key observations

  1. Website uses WordPress CMS with Themify Ultra theme and multiple plugins
  2. Cookie consent mechanism is implemented with detailed categories but no explicit privacy policy page found
  3. No visible contact emails or physical addresses in provided HTML; phone numbers implied via analytics scripts but not explicitly labeled on page
  4. Social media presence is strong with official Facebook, Twitter, LinkedIn, YouTube, Instagram links in JSON-LD
  5. No visible security.txt or vulnerability disclosure policy
  6. No explicit terms of service or privacy policy pages detected in provided content
  7. Website is well structured with clear navigation menus and good SEO metadata
  8. HTTPS is enabled and multiple Google tracking scripts are used
  9. No WAF or blocking mechanisms detected
  10. WHOIS data supports domain legitimacy and long-term operation
Technical notes

Notes

The website is built on a modern WordPress platform with a well-maintained theme and multiple plugins enhancing functionality such as sliders, forms, cookie management, and analytics. The use of Google Analytics and Tag Manager indicates a mature approach to data-driven insights. Performance is moderate with some preloading and prefetching optimizations. Mobile responsiveness is good, supported by CSS media queries and adaptive layouts. Accessibility features are basic but present, including skip links and ARIA labels. SEO is enhanced by structured data (JSON-LD) and meta tags. Technical risks include potential plugin vulnerabilities if not regularly updated and lack of advanced security headers. Overall, the technical infrastructure supports business operations effectively with opportunities for modernization and security hardening.
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 iem.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 iem.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.