Skip to main content

Security report for dmarc.io

dmarcian · Technology · N/a

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

Security score

68/100

Risk levelMedium

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

dmarc.io is a specialized resource center focused on DMARC (Domain-based Message Authentication, Reporting & Conformance) compliance and email security. Powered by dmarcian.com, it provides public information about DMARC sources, forwarders, and best practices for sending email on behalf of others. The site targets deployers, operators, and developers interested in DMARC deployment and compliance. It operates as a niche information repository with a clear focus on email authentication and security standards. Technically, the website uses modern JavaScript modules and integrates analytics tools such as Google Tag Manager and Hotjar for user behavior tracking. Hosting and DNS services are provided by Google Cloud DNS. However, the site lacks a valid SSL/TLS certificate and does not serve content over HTTPS, which is a significant security shortfall. Performance is moderate, with a page load time of approximately 3.7 seconds and a moderate number of resources. From a security perspective, the site enforces a strict DMARC policy at the DNS level with a reject policy, which is a strong positive indicator for email security. However, the absence of HTTPS, lack of security headers, and missing advanced TLS protocols reduce the overall security posture. No privacy or cookie policies are present, and no contact forms or direct contact information are provided on the site, limiting transparency and compliance with privacy regulations. Overall, dmarc.io serves as a valuable technical resource for DMARC-related information but requires significant improvements in web security practices, privacy compliance, and transparency to enhance trustworthiness and user confidence.

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. 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 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 dmarc.io

This scan found 17 issues across 5 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
100
Security headers
15
Email security
85
DNS health
70
Network security
100
GDPR outside view
40
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

Technical appendix

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

Business context

Business profile

dmarc.io occupies a niche market position as a public repository and resource center for DMARC compliance information, powered by the parent company dmarcian.com. Its business model revolves around providing free, publicly accessible data and guidance to organizations and individuals deploying DMARC. The site supports the broader ecosystem of email security by offering tools and information that help improve DMARC adoption and enforcement. The target audience includes technical professionals responsible for email infrastructure and security, such as system administrators, security engineers, and developers. The partnership with dmarcian.com and the linked community forum indicate a collaborative ecosystem approach. Revenue streams are likely indirect, supporting dmarcian.com's commercial offerings through brand awareness and community engagement. Growth indicators include active community discussions and integration with dmarcian.com's services. However, the lack of direct contact information and formal policies may limit broader enterprise adoption. Strategic partnerships and enhanced compliance features could improve market penetration and trust.

Security posture

The current security posture of dmarc.io is moderate but with critical gaps. The DNS configuration shows a strict DMARC policy with reject, which is a strong control against email spoofing and phishing. SPF is configured with a fail-all policy, further strengthening email authentication. However, the absence of a valid SSL/TLS certificate and lack of HTTPS support is a major vulnerability, exposing users to potential interception and undermining trust. No HTTP security headers are present, and no modern TLS protocols are enabled, indicating outdated or incomplete server security configurations. No privacy or cookie policies are published, which is a compliance gap under GDPR and other privacy regulations. Incident response and security policy information are not disclosed, limiting transparency and preparedness. Overall, while email security controls are strong at the DNS level, web security practices require urgent improvement to protect users and comply with modern standards.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security with preload and includeSubDomains.
  3. Publish clear privacy and cookie policies with consent mechanisms to improve compliance and user trust.
  4. Provide visible contact information including security incident response contacts (e.g., security@ or abuse@ emails).
  5. Regularly audit and update server TLS configurations to support modern protocols (TLS 1.2/1.3) and enable OCSP stapling and session resumption.
Technical notes

Notes

The website is built using modern JavaScript ES modules and leverages third-party analytics and tracking tools such as Google Tag Manager and Hotjar. DNS is managed via Google Cloud DNS with multiple Google nameservers, indicating reliable hosting infrastructure. Performance is moderate with a page load time of approximately 3.7 seconds and a page size of about 681 KB, which is acceptable but could be optimized. Mobile optimization is good, and accessibility is basic but present. No CMS or major web frameworks are detected, suggesting a custom or lightweight frontend implementation. The lack of HTTPS and security headers represents technical debt and a security risk. The site uses SVG graphics extensively for branding and UI elements. Overall, the technical infrastructure is modern but requires improvements in security and privacy implementations to reduce risks and enhance user experience.
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 dmarc.io. 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 dmarc.io.

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.