Skip to main content

Security report for memoriams.com

Memoriams · Media · N/a

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

66/100

Risk levelMedium

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

Memoriams operates as a specialized B2B platform providing funeral professionals with an exclusive network to price and place obituaries in thousands of newspapers. The company positions itself as a trusted partner endorsed by the Local Media Consortium, emphasizing ease of use, real-time pricing, and customer service. The website content is professionally crafted to appeal to funeral homes, offering a streamlined obituary placement process with preview capabilities and multi-publication submission options. Technically, the website is built on ASP.NET Web Forms with a front-end leveraging Bootstrap and jQuery 1.7.1. It integrates multiple analytics and marketing tools including Google Analytics, Google Tag Manager, and Tealium. The site is mobile optimized and presents a good user experience with clear navigation and professional design. However, some technical debt is evident in the use of an outdated jQuery version and minimal security headers. From a security perspective, the site employs a Content-Security-Policy header and secure form submission practices but lacks other important headers such as HSTS and X-Frame-Options. No vulnerabilities or exposed sensitive data were detected, but the absence of a cookie consent mechanism and minimal privacy compliance indicators suggest room for improvement. The WHOIS data is unavailable, which raises questions about domain registration transparency but does not directly impact the site's operational legitimacy. Overall, Memoriams presents a credible and professional online presence with moderate technical maturity and a solid business model. Strategic improvements in security headers, privacy compliance, and domain registration transparency would enhance trust and reduce risk.

Scanned

NIS2 and GDPR posture

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

6 findings rated critical or high. Fix these first.

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

  2. 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 memoriams.com

This scan found 22 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
30
Email security
60
DNS health
80
Network security
100
GDPR outside view
53
Average
66

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

Memoriams occupies a niche market within the media sector, focusing on obituary placement services for funeral homes. Its competitive advantage lies in an exclusive network of over 3,000 publications and endorsement by the Local Media Consortium, which strengthens its market credibility. The business model is service-oriented, providing a platform that simplifies obituary pricing and submission, likely generating revenue through service fees or partnerships with publications. The target customers are funeral professionals seeking efficiency and reliability. The presence of customer testimonials and dedicated support channels indicates a customer-centric approach. The company appears to have a medium-sized operation with over a decade of experience, though no explicit founding date or parent company information is available. The lack of visible social media presence may limit broader market engagement but does not detract from its specialized focus.

Security posture

The website demonstrates a moderate security posture with implementation of a Content-Security-Policy header and secure form handling via ASP.NET Web Forms. Input validation is present on login forms, reducing risk of injection attacks. However, the absence of additional security headers such as Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options limits protection against common web threats. The use of an outdated jQuery version introduces potential vulnerabilities. No evidence of exposed sensitive data or known vulnerabilities was found. Privacy compliance is basic, lacking cookie consent mechanisms and explicit GDPR indicators. Incident response and security policy information are not publicly available, which may impact transparency and readiness. Overall, the security posture is adequate for a medium-sized B2B service but would benefit from enhancements to align with best practices and regulatory requirements.

Recommendations

  1. Implement additional security headers including Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options to strengthen web security.
  2. Upgrade jQuery and other JavaScript libraries to current versions to mitigate known vulnerabilities.
  3. Add a cookie consent banner and update privacy policies to explicitly address GDPR and other privacy regulations.
  4. Clarify domain registration details and ensure WHOIS information is accurate and publicly available to improve trustworthiness.
  5. Develop and publish security policies and incident response procedures to enhance transparency and preparedness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Memoriams
Description
Memoriams provides funeral professionals with an exclusive network to place obituaries in newspapers. It offers pricing, deadlines, and preview services for obituaries across thousands of newspapers at no cost to funeral homes.
Key services
Obituary pricing, Obituary placement in newspapers, Preview of obituaries before submission, Customer support for obituary placement
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.7.1, Bootstrap CSS, Google Analytics, Google Tag Manager, ASP.NET Web Forms
Frameworks
ASP.NET
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • Content-Security-Policy header implemented
  • Secure form submission via POST
  • Input validation on login form

Analytics and tracking

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

Advertising

Ad networks
DoubleClick
Tracking pixels
Adobe Demdex
Marketing tools
Tealium (utag.js)
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF detected.
  2. Content is professionally presented and targeted at funeral professionals.
  3. No DNSSEC or WHOIS registration data available, which is unusual for a .com domain.
  4. Multiple analytics and tracking scripts are used, but no cookie consent mechanism is present.
  5. Security headers are minimal but include a Content-Security-Policy.
  6. Login form uses ASP.NET Web Forms with client-side validation.
  7. Contact information is clearly provided with phone and email.
  8. Privacy and Terms of Use pages are linked and present.
  9. No social media links detected in the HTML content.
Technical notes

Notes

The website is built on a legacy ASP.NET Web Forms framework with front-end technologies including Bootstrap and an outdated jQuery version (1.7.1). It integrates multiple third-party analytics and marketing tools such as Google Analytics, Google Tag Manager, and Tealium, indicating a mature approach to user tracking and marketing. The site is mobile responsive and uses a Content-Security-Policy header, reflecting some modern security awareness. However, the lack of other security headers and the use of older JavaScript libraries suggest technical debt and potential security risks. Performance is moderate with asynchronous loading of scripts. The absence of a CMS or modern platform reduces flexibility but may simplify maintenance. Overall, the technical infrastructure is functional but would benefit from modernization and enhanced security controls.
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 memoriams.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 memoriams.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.