Skip to main content

Security report for formstack.io

Technology · United States

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

Security score

67/100

Risk levelMedium

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

The website at formstack.io currently presents minimal accessible content, lacking metadata, privacy policies, contact information, and visible business descriptions. The domain is registered through a privacy protection service with a reputable registrar and has a reasonable age consistent with a legitimate technology company. The technical infrastructure includes JavaScript and CSS resources loaded from formstack.io subdomains and is hosted on Microsoft Azure DNS servers. However, the site lacks visible security headers, HTTPS confirmation, and accessibility or SEO optimizations, indicating a low level of digital maturity. Security posture is weak due to missing HTTPS and security policies, and no incident response or vulnerability disclosure information is available. Overall, the site appears to be a placeholder or minimal form hosting page rather than a fully developed business website.

Scanned

NIS2 and GDPR posture

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

9 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 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';…
  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

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

Keep watching formstack.io

This scan found 20 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
82
Security headers
40
Email security
55
DNS health
75
Network security
100
GDPR outside view
50
Average
67

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 formstack.io, from OffSeq Breach.

Total records
3
Employees
0
Customers
3
Third parties
0
Weak passwords
0%

1 subdomain 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 formstack.io.

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

Formstack.io operates in the technology sector, likely providing form hosting or form engine services as indicated by script sources. The domain age and registrar suggest a stable presence since 2017. However, the lack of visible business information, contact details, or policies limits insight into market positioning, revenue streams, or partnerships. The business model appears to be service-oriented, focusing on form management or data collection solutions. The absence of marketing or analytics tools suggests limited active customer engagement on this particular page.

Security posture

The security posture is currently weak due to the absence of HTTPS confirmation, security headers, and privacy or cookie policies. No incident response or vulnerability disclosure mechanisms are evident. The use of privacy protection for WHOIS is justified but limits transparency. No exposed vulnerabilities or sensitive data were detected in the minimal content. The site would benefit from implementing standard security best practices including HTTPS, security headers, and clear privacy and incident response policies to improve trust and compliance.

Recommendations

  1. Implement HTTPS with valid SSL/TLS certificates to secure data in transit.
  2. Add comprehensive privacy and cookie policies with GDPR compliance indicators.
  3. Include contact information and incident response channels for transparency and trust.
  4. Enable security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Improve website content quality and navigation to enhance user experience and business credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
moderate

Technology

Stack
JavaScript
Performance
moderate
Mobile
poor
Accessibility
poor
SEO
poor

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 minimal and lacks substantive information.
  2. No metadata such as title or description present.
  3. No privacy, cookie, or terms of service policies found.
  4. No contact information or forms detected.
  5. External scripts and stylesheets are loaded from formstack.io subdomains.
  6. No social media or external links present in the HTML.
  7. No security headers or HTTPS information available from provided data.
  8. Domain is privacy protected but registered with a reputable registrar and has a reasonable age.
  9. No adult or explicit content detected; content is safe for general audiences.
  10. Website appears to be a placeholder or minimal form hosting page.
Technical notes

Notes

The website uses JavaScript and CSS loaded from formstack.io subdomains, hosted on Microsoft Azure DNS infrastructure. The HTML content is minimal with no metadata or SEO tags, indicating a basic technical implementation. No CMS or frameworks are detected. Performance is likely moderate given external resource loading but cannot be fully assessed. Mobile optimization and accessibility are poor due to lack of content and structure. Technical debt is evident in missing security features and lack of content, suggesting modernization opportunities to improve digital presence and security posture.
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

Earlier scans of this domain

  1. 61/100Medium31 findingsView report
Reviews of this site

Share your experience with formstack.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 formstack.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.