cryptpad.org - DNS, WHOIS, DMARC and SPF of the domain name

Summary

Registrar: OVH sas
Status: clientDeleteProhibited
Created on: April 16, 2018
Expires on: April 16, 2027
Name servers: dns100.ovh.net, ns100.ovh.net
Mail servers: mail.cryptpad.org
DMARC: Reject
SPF: Strict
DKIM: 2 keys found
Website: See the website

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from cryptpad.org but fails SPF and DKIM checks.

Policy: Reject
Subdomain policy: Reject
Messages covered: 100%
DKIM alignment: Strict
SPF alignment: Strict
Aggregate reports: [email protected]
Failure reports: [email protected]

Record

v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:[email protected]!10m; ruf=mailto:[email protected]!10m; rf=afrf; fo=1; ri=86400; adkim=s; aspf=s

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for cryptpad.org.

Rule	Value	Result
include	spf.mailjet.com	Allowed
ip4	54.36.1.148	Allowed
ip6	2001:41d0:128:f004::1	Allowed
all	—	Rejected

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:spf.mailjet.com ip4:54.36.1.148 ip6:2001:41d0:128:f004::1 -all

E-mail signing (DKIM)

DKIM keys published by cryptpad.org under the most common selectors. Other keys may exist under selectors specific to each sending service.

Selector	Likely service	Key	Status
mailjet	Mailjet	RSA 2048 bits	Active
dkim	—	RSA 2048 bits	Active

MX, SPF, DKIM and DMARC: the e-mail records

Four DNS records make a domain's e-mail work. MX says where e-mails sent to cryptpad.org arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from cryptpad.org was really sent by this domain, which protects it against spoofing.

MX

An MX (Mail Exchanger) record designates a server that receives e-mails sent to the domain. When someone writes to an @cryptpad.org address, their mail server queries the DNS for the domain's MX records, then delivers the message to the server they point to.

Example record

cryptpad.org  MX  10 mx1.cryptpad.org.
cryptpad.org  MX  20 mx2.cryptpad.org.

What the record contains

10, 20: Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.cryptpad.org.: Host name of the mail server. It must point to an A or AAAA record: an IP address or an alias (CNAME) is not allowed here.
0 .: An MX "0 .", called a null MX, declares that the domain accepts no e-mail: sending servers give up at once instead of retrying.

Declaring at least two servers with different priorities avoids losing e-mails during an outage: sending servers retry for several days and fall back on the backup server. Without any MX, they try to deliver directly to the IP address of the domain.

SPF

SPF (Sender Policy Framework) is a TXT record listing the servers allowed to send e-mails on behalf of the domain. The receiving server checks that the sender is on this list. The final "all" rule says what to do with other servers: reject them (-all), flag their e-mails as suspicious (~all) or make no decision (?all).

Example record

cryptpad.org  TXT  "v=spf1 mx include:_spf.google.com ip4:192.0.2.10 -all"

What the record contains

v=spf1: Identifies the record as an SPF policy. It must come first.
ip4, ip6: Allows a specific IP address or an address range, for example ip4:192.0.2.0/24.
a, mx: Allows the addresses of the domain itself (A record) or those of its mail servers (MX).
include: Allows the servers of another domain, usually a sending service: include:_spf.google.com for Google Workspace.
-all, ~all: Final rule, applied to every other server. Its qualifier decides what happens to them: - rejects them, ~ flags their e-mails as suspicious, ? makes no decision, + accepts them (avoid it).

A domain must publish only one SPF record, and its evaluation cannot exceed 10 DNS lookups (include, a, mx, exists, redirect). Beyond that, mail servers treat it as invalid.

DKIM

DKIM (DomainKeys Identified Mail) signs every outgoing e-mail with a private key. The matching public key is published in a TXT record at selector._domainkey.cryptpad.org, so the recipient can check that the message really comes from the domain and was not altered on the way. The selector is chosen by each sending service and cannot be guessed: Dataweaz checks the most common ones (Google Workspace, Microsoft 365, Mailchimp, SendGrid…), so a key published under another selector may exist without appearing here.

Example record

google._domainkey.cryptpad.org  TXT  "v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA…"

What the record contains

v=DKIM1: Protocol version. Optional but recommended, in which case it must come first.
k: Key algorithm: rsa, the most common, or ed25519.
p: Public key, base64-encoded. An empty value means the key has been revoked.
t: Flags: y marks a key in testing, whose failures must not be penalized; s forbids its use for subdomains.

Each sending service publishes its key under its own selector (google, selector1, k1…), which allows several keys and seamless rotation. A 2048-bit RSA key is recommended today.

DMARC

DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF and DKIM. Published on _dmarc.cryptpad.org, it tells mail servers what to do with an e-mail that fails these checks (let it through, send it to spam or reject it) and where to send reports.

Example record

_dmarc.cryptpad.org  TXT  "v=DMARC1; p=quarantine; rua=mailto:[email protected]; adkim=r; aspf=r"

What the record contains

v=DMARC1: Identifies the record as a DMARC policy. It must come first.
p: Policy applied to e-mails that fail the checks: none (monitoring only), quarantine (spam folder) or reject.
sp: Subdomain policy. Without it, subdomains follow the domain's policy.
rua: Address that receives daily aggregate reports about e-mails sent on behalf of the domain, whether they pass the checks or not.
ruf: Address that receives detailed failure reports, message by message. Few providers still send them.
pct: Percentage of e-mails subject to the policy, for a gradual rollout. 100 by default.
adkim, aspf: DKIM and SPF alignment: r (relaxed, a subdomain of the same domain is enough) or s (strict, the domain must be identical).

To roll out DMARC without blocking legitimate e-mails, start with p=none and an rua address, analyze the reports to find every service sending on behalf of the domain, then move to quarantine and finally to reject.

DNS records of cryptpad.org

IP addresses (A and AAAA)

An A record maps the domain name to an IPv4 address: the address of the server that browsers contact to display the website. The AAAA record does the same for an IPv6 address. A domain can have several of them to spread visits across several servers.

Type	IP address
A	92.222.135.200
AAAA	2001:41d0:128:f004::3

Name servers (NS)

NS records designate the authoritative DNS servers of the domain: they answer every question about its other records (A, MX, TXT…). They are provided by the registrar, the hosting provider or a dedicated DNS service, and several servers are declared so that the domain keeps working if one of them fails.

Server	IP address
dns100.ovh.net	5.135.250.177
ns100.ovh.net	5.135.44.185

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @cryptpad.org addresses. Each server has a priority: the one with the lowest number is tried first, the others take over if it fails. Without an MX record, the domain cannot receive e-mails.

Priority	Server	IP address
1	mail.cryptpad.org	54.36.1.148

TXT records

TXT records hold free text. They are used to prove ownership of the domain to online services (Google, Microsoft, Facebook…) and to publish e-mail security rules: SPF on the domain itself, DMARC on _dmarc.cryptpad.org.

Name	Content
cryptpad.org	v=spf1 include:spf.mailjet.com ip4:54.36.1.148 ip6:2001:41d0:128:f004::1 -all
_dmarc.cryptpad.org	v=DMARC1; p=reject; sp=reject; pct=100; rua=mailto:[email protected]!10m; ruf=mailto:[email protected]!10m; rf=afrf; fo=1; ri=86400; adkim=s; aspf=s
mailjet._domainkey.cryptpad.org	k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA0au5SLalde3SgdJEe8yvTLIC4qA6EhDMdWVsSBl87zteUyG7x5/NTi+2HHmTkWeD0JoVWbrUe+RzpjX1e5KF9GYdhAaxIexhtJaWUUPpUK2xgkstD6b/v+A0Tq/wpY0sgihKRQhw9+99UkY0VNaU4NnVPlmrqmNiVgXF3CYSasZi6DlESRwlzEcrvYQ75dMxr8C3HcNQdGUFnSRZjfgUhDWCZbvQDVY4gqZEaWtyD4hF+CTw+cG9vIDalYOQgla44xu3Mln8su0FzSYioCsC/oCELZAwu/ZDCuQbAJAL/fL8Z88StHKVT08anJoGmL5nBGIjZAXQoul6/kY6W8BkfwIDAQAB
dkim._domainkey.cryptpad.org	v=DKIM1;k=rsa;s=email;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAuZnCJq9Jm206pX/eRadxgHnlKkDtnpkWlkUy8nVlBpj1fCdgEmRdlixIMJDYFs5745p+/V1l5qMBG796sCWRjh7BKMrDEB8V7cmXHbW2oGAxaeRT2eeOFdKTR4hVAw5KpxPwgKkV4w91aIFKlHuaaVXar20msxPsDKOc85xE8nUfSwItcBZ4J5UKNTNhom3qrqug18MmpuMn1OL4iR95FBOBJq+0Vhrd9xW+Ap/5+DJFma54LSAtJcGWOz/hn+dq+olnPn1HlKLAxyJeWzSqSBrAN4suJExr+7qZ30mDT4fYQyXY1jzD1icgD+moROGy+y5pX4PjvN3Tl0t18uTMPQIDAQAB;t=s;

Related IP addresses

IPv4 addresses used by cryptpad.org: website, name servers, mail servers and senders authorized by SPF.

IP address	Used for	/24 block
92.222.135.200	Website	92.222.135.0/24
5.135.250.177	Name server dns100.ovh.net	5.135.250.0/24
5.135.44.185	Name server ns100.ovh.net	5.135.44.0/24
54.36.1.148	Mail server mail.cryptpad.org, Authorized by SPF	54.36.1.0/24

WHOIS of the domain cryptpad.org

Domain Name: cryptpad.org
Registry Domain ID: REDACTED
Registrar WHOIS Server: http://whois.ovh.com
Registrar URL: http://www.ovh.com
Updated Date: 2026-08-12T02:16:35Z
Creation Date: 2018-04-16T17:10:14Z
Registry Expiry Date: 2027-04-16T17:10:14Z
Registrar: OVH sas
Registrar IANA ID: 433
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.972101007
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: dns100.ovh.net
Name Server: ns100.ovh.net
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-01T15:49:01Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Terms of Use: Access to Public Interest Registry WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the Public Interest Registry registry database. The data in this record is provided by Public Interest Registry for informational purposes only, and Public Interest Registry does not guarantee its accuracy. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Identity Digital except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Public Interest Registry reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.  The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Domain Name: cryptpad.org
Registry Domain ID: REDACTED FOR PRIVACY
Registrar WHOIS Server: whois.ovh.com
Registrar URL: https://ovh.com
Updated Date: 2025-05-31T17:10:40Z
Creation Date: 2018-04-16T17:10:14Z
Registrar Registration Expiration Date: 2027-04-16T19:10:14+02:00
Registrar: OVH, SAS
Registrar IANA ID: 433
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.972101007
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: REDACTED FOR PRIVACY
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: FR
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext: REDACTED FOR PRIVACY
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext: REDACTED FOR PRIVACY
Registrant Email: REDACTED FOR PRIVACY - Send message to contact by visiting https://ovhcloud.com/en/lp/request-ovhcloud-registered-domain/
Registry Admin ID: REDACTED FOR PRIVACY
Admin Name: REDACTED FOR PRIVACY
Admin Organization: REDACTED FOR PRIVACY
Admin Street: REDACTED FOR PRIVACY
Admin City: REDACTED FOR PRIVACY
Admin State/Province: REDACTED FOR PRIVACY
Admin Postal Code: REDACTED FOR PRIVACY
Admin Country: FR
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext: REDACTED FOR PRIVACY
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext: REDACTED FOR PRIVACY
Admin Email: REDACTED FOR PRIVACY - Send message to contact by visiting https://ovhcloud.com/en/lp/request-ovhcloud-registered-domain/
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech City: REDACTED FOR PRIVACY
Tech State/Province: REDACTED FOR PRIVACY
Tech Postal Code: REDACTED FOR PRIVACY
Tech Country: FR
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: REDACTED FOR PRIVACY - Send message to contact by visiting https://ovhcloud.com/en/lp/request-ovhcloud-registered-domain/
Name Server: ns100.ovh.net
Name Server: dns100.ovh.net
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System:
http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-04-16T00:10:31Z <<<

For more information on Whois status codes, please visit https://icann.org/epp 

###############################################################################
#
# Welcome to the OVH WHOIS Server.
#
# whois server  : whois.ovh.com       check server  : check.ovh.com
#
# The data in this Whois is at your disposal  with the aim of supplying you the
# information only,  that is helping you  in the obtaining  of  the information
# about  or  related to a domain name registration record.   OVH Sas  make this
# information available "as is", and  do not  guarantee its accuracy.  By using
# Whois,  you agree that you will use these data  only for  legal  purposes and
# that,  under no circumstances will you use this data to:  (1) Allow,  enable,
# or  otherwise  support  the  transmission  of  mass  unsolicited,  commercial
# advertisement  or  roughly  or  requests  via the  individual mail (courier),
# the E-mail (SPAM), by telephone or by fax. (2) Enable high volume, automated,
# electronic  processes  that  apply  to  OVH  Sas   (or its computer systems).
# The copy,   the compilation,   the re-packaging,   the dissemination   or the
# other  use  of  the Whois base  is  expressly  forbidden  without  the  prior
# written consent of  OVH.  Domain  ownership  disputes should be settled using
# ICANN's Uniform Dispute Resolution Policy: http://www.icann.org/udrp/udrp.htm
# We reserve the right  to  modify  these  terms  at  any  time.  By submitting
# this query,  you agree to  abide by these terms.  OVH Sas  reserves the right
# to  terminate  your  access  to  the  OVH Sas  Whois  database  in  its  sole
# discretion,   including   without   limitation,   for  excessive  querying of
# the Whois database  or  for  failure  to  otherwise  abide  by  this  policy.
#
# L'outil du Whois  est  à  votre  disposition  dans  le  but  de  vous fournir
# l'information  seulement,  c'est-à-dire  vous   aider   dans  l'obtention  de
# l'information  sur ou lié à un  rapport  d'enregistrement  de nom de domaine.
# OVH Sas rend  cette information disponible  "comme est,"  et  ne garanti pas
# son exactitude. En utilisant  notre outil  Whois, vous  reconnaissez que vous
# emploierez ces données seulement pour  des buts légaux et ne pas utiliser cet
# outil dans les buts suivant: (1) la transmission de publicité non sollicitée,
# commerciale massive ou en gros ou des sollicitations via courrier individuel,
# le courrier électronique (c'est-à-dire SPAM),  par  téléphone ou par fax. (2)
# l'utilisation d'un grand volume,  automatisé  des processus électroniques qui
# soulignent ou chargent ce système de base de données  Whois  vous fournissant
# cette  information.   La  copie   de  tout  ou  partie,   la compilation,  le
# re-emballage,  la dissémination ou d'autre utilisation de la base Whois  sont
# expressément interdits sans consentement écrit antérieur de OVH. Un désaccord
# sur la possession d'un nom de domaine peut être résolu en suivant la  Uniform
# Dispute  Resolution  Policy  de  l'ICANN:  http://www.icann.org/udrp/udrp.htm
# Nous nous  réservons  le  droit  de  modifier  ces  termes  à tout moment. En
# soumettant une requête au Whois vous consentez à vous soumettre à ces termes.

# local time : 2026-10-01T15:49:01Z
# gmt time : 2026-10-01T15:49:01Z
# last modify : 2026-04-16T00:10:31Z

% Query time: 680 msec
% WHEN: Thu Oct 01 15:49:00 UTC 2026