secutils.dev valid

Secutils.dev Documentation

Documentation and guides for Secutils.dev - an open-source, versatile toolbox for security-minded engineers.

For agents: Open-source toolbox for security engineers with guides for digital certificates, webhook responders and key conversion; documentation of its workspace tools.

open-source security toolboxdigital certificateswebhooksweb cryptojwk conversion

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-24T06:22:33.408Z. Cached copy · Source on secutils.dev

# Secutils.dev Documentation

> Documentation and guides for Secutils.dev - an open-source, versatile toolbox for security-minded engineers.

Full Secutils.dev documentation (all guides) in one markdown document for LLM and offline use.

## What is Secutils.dev?

# What is Secutils.dev?

Secutils.dev is an [open-source](https://github.com/secutils-dev) security toolbox for engineers. It brings together the utilities you need to develop and test secure web applications - webhook responders, certificate generation, content security policies, and web page tracking - all in one straightforward interface.

![Secutils.dev workspace hub](https://secutils.dev/docs/assets/images/workspace_hub-6eea8d2d05fe1f89983a29af9a482663.png)

## What can you do with it?

- **Webhooks** - Create mock HTTP APIs, test webhook integrations, and set up honeypot endpoints with custom JavaScript logic.
- **Digital Certificates** - Generate X.509 certificate templates and manage private keys for HTTPS, code signing, and more.
- **Content Security Policy** - Create, import from a live URL, and test Content Security Policies for your web applications.
- **Web Scraping** - Track changes in web pages and API responses over time with scheduled checks and notifications.

Head over to the [Guides](https://secutils.dev/docs/category/guides) to see each tool in action, or sign in and start exploring from the workspace hub.

## Get involved

If you have a question or idea, we encourage you to use [GitHub Discussions](https://github.com/secutils-dev/secutils/discussions). For bug reports, please submit them directly to [GitHub Issues](https://github.com/secutils-dev/secutils/issues). If you need to contact us for anything else, feel free to do so using the "Contact" form.

## Digital Certificates ➔ Certificate templates

# What is a digital certificate?

A digital certificate, also known as an SSL/TLS certificate or public key certificate, is a digital document that verifies the identity of a website, server, or other digital entity, and allows secure communication between two parties by encrypting data sent over the internet. It contains information about the identity of the certificate holder, such as their name and public key, and is issued by a trusted third-party Certificate Authority (CA).

There are different types of digital certificates that can be generated with various parameters. Certificates can be password-protected, can be bundled with the keys, can rely on different cryptographic algorithms, and eventually expire. Considering these factors, it can be challenging to develop and test web applications that rely on digital certificates.

On this page, you can find guides on creating digital certificate templates with parameters that match your specific needs.

## Generate a key pair for a HTTPS server

In this guide you'll create a template for generating a private key and self-signed certificate for a Node.js HTTPS server:

1. ![Navigate to Digital Certificates → Certifica
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=secutils.dev · GET /v1/domain/secutils.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for secutils.dev:
1. POST https://agentwebmap.com/v1/sites/secutils.dev/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://secutils.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/secutils.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/secutils.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.