Dataweaz

jotform.com

Summary

Registrar
Tucows Domains Inc.
Status
clientTransferProhibited
Created on
November 10, 2005
Expires on
November 10, 2034
Name servers
leah.ns.cloudflare.com, jay.ns.cloudflare.com
Mail servers
aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx2.googlemail.com, aspmx3.googlemail.com
DMARC
Reject

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 jotform.com but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1; adkim=r; aspf=r;

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for jotform.com.

RuleValueResult
ip4152.160.0.0/16Allowed
ip423.251.253.0/24Allowed
ip4152.232.87.0/24Allowed
ip4209.127.149.0/24Allowed
ip4212.47.85.0/24Allowed
includeamazonses.comAllowed
include_spf.google.comAllowed
include4773329.spf02.hubspotemail.netAllowed
all—Rejected

Top-level DNS lookups: 3 of 10 allowed

Record

v=spf1 ip4:152.160.0.0/16 ip4:23.251.253.0/24 ip4:152.232.87.0/24 ip4:209.127.149.0/24 ip4:212.47.85.0/24 include:amazonses.com include:_spf.google.com include:4773329.spf02.hubspotemail.net -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
mail—RSA 1024 bits · shortActive

RSA keys shorter than 2048 bits, called short keys, are discouraged: they are easier to break.

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 jotform.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from jotform.com 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 @jotform.com 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

jotform.com  MX  10 mx1.jotform.com.
jotform.com  MX  20 mx2.jotform.com.

What the record contains

10, 20
Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
mx1.jotform.com.
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

jotform.com  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.jotform.com, 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.jotform.com  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.jotform.com, 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.jotform.com  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 jotform.com

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.

TypeIP address
A34.102.158.113

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.

ServerIP address
leah.ns.cloudflare.com108.162.192.129
jay.ns.cloudflare.com108.162.193.123

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @jotform.com 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.

PriorityServerIP address
10aspmx.l.google.com172.253.143.27
20alt2.aspmx.l.google.com142.251.127.27
20alt1.aspmx.l.google.com192.178.213.27
30aspmx2.googlemail.com192.178.213.26
30aspmx3.googlemail.com142.251.127.26

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.jotform.com.

NameContent
jotform.comopenai-domain-verification=dv-45gaHepX9eTJI2gYExR4OWWC
jotform.comv=MCPv1; k=ed25519; p=Lb8maLkEb+gZXcnSZFr4TAFCi7UoFZV++O+WBDFldYA=
jotform.comshopify_verification_store=OZBLVFVJ
jotform.comMS=DEB2999CDE6BA3AC00C864C3126A6D4472F4DC8A
jotform.comelevenlabs=kN2-MsgJDJnXKT2MbTaOMCuqDz3RxsGY_HydqGukqCs
jotform.com1password-site-verification=YQFQJ47QRJG5XBU3T4RISJKW3Q
jotform.comspf2.0/pra ip4:152.160.0.0/16 ip4:23.251.253.0/26 ip4:152.232.87.0/24 ip4:209.127.149.0/24 ip4:212.47.85.0/24 include:amazonses.com include:_spf.google.com include:4773329.spf02.hubspotemail.net -all
jotform.comZOOM_verify_3witIxeKC0CNK5NwDV0SDg
jotform.comgoogle-site-verification=yMxy0UgVeqRNu6CSLRHVC2HmunJDTMzY8LtuodbuICs
jotform.comh1-domain-verification=ZtPHS7v95dFAHaPo8aiXkokpS6acwZuF2RXR5gLiERPFPj2H
jotform.comMS=ms75652662
jotform.comgoogle-site-verification=dzI_jhaY6WEaI_W4_ibtid7sgDCf9xbKxJtNCx-VBwY
jotform.comopenai-domain-verification=dv-FyHKj2aBDgIx5yO1XKhP76Fx
jotform.comyahoo-verification-key=badZkLQsw6G2ONbbr8U24IacoTzKB/h933ItHATNN9k=
jotform.comopenai-domain-verification=dv-JoBa3T0S1jxNwWtCLacI5eRK
jotform.comhubspot-developer-verification=Njk3N2RjNzEtZTc1MC00ZDJlLWJmZjQtOWJhNmIyYmUyMTdh
jotform.comtwilio-domain-verification=424f03e983ff51a3db9362d75900bb3b
jotform.comblitz=mu-f7d86c61-76376714-55e3b491-cf0e7819
jotform.comv=spf1 ip4:152.160.0.0/16 ip4:23.251.253.0/24 ip4:152.232.87.0/24 ip4:209.127.149.0/24 ip4:212.47.85.0/24 include:amazonses.com include:_spf.google.com include:4773329.spf02.hubspotemail.net -all
jotform.comcursor-domain-verification-vmeym2=EtY1BkLbyPlFzt9Sw7KrMSYHl
jotform.comapple-domain-verification=UM5LzvIAJSWlUNnf
_dmarc.jotform.comv=DMARC1; p=reject; pct=100; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=1; adkim=r; aspf=r;
google._domainkey.jotform.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAgKOTl0c0QL51w6LOOH5gryZQ8x2OwaODW7SYBKGICctUweUPjUU/Ta/7sFLzwF54SAyAWg63Ax+ZEckt4uqmQpUNZuiZcgXlbNYT9XFTq1ns2kPGeT3Pj0h3KRDp1QE7uRr5dr1Kl62vMOgZ7cjjQeOpeY5VEJoW5U4Ai7tVJnxRMeQ8uIC9MlrQNM86Y7JtiOn2l6uGLpT/4MSfLfJhrSCyGmoVcP0YFl+4aOXVIF9Bf86II+inI4sBX2Nh1bR0QU21oa0oBHkCWZU7eUSTloTh1my1En6MPR2ji6GEyha5z4VhFKLlKxvtu9+Mv8QiAKZcOB/JG1vvcs+6unRiQwIDAQAB
mail._domainkey.jotform.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC0l/FM7aefceaRQsCFT47NfDTTx+tV3wK8wqKb66yUIKlP1gZAOyHyBcfMq4iaqnKN+h9+KXwq7LA3hlzXk8y4ceGDIOePT4eupP0CWKDLO79/6xrUWubl8Bkwe3QfrWQrq646j4cqfURzegI3bxqXucdi/4N9oz0wg9SWjNaUcQIDAQAB

Related IP addresses

IPv4 addresses used by jotform.com: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
34.102.158.113Website34.102.158.0/24
108.162.192.129Name server leah.ns.cloudflare.com108.162.192.0/24
108.162.193.123Name server jay.ns.cloudflare.com108.162.193.0/24
172.253.143.27Mail server aspmx.l.google.com172.253.143.0/24
142.251.127.27Mail server alt2.aspmx.l.google.com142.251.127.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com192.178.213.0/24
192.178.213.26Mail server aspmx2.googlemail.com192.178.213.0/24
142.251.127.26Mail server aspmx3.googlemail.com142.251.127.0/24

WHOIS of the domain jotform.com

Domain Name: JOTFORM.COM
   Registry Domain ID: 251780069_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.tucows.com
   Registrar URL: http://www.tucows.com
   Updated Date: 2025-06-10T11:04:36Z
   Creation Date: 2005-11-09T23:12:11Z
   Registry Expiry Date: 2034-11-09T23:12:11Z
   Registrar: Tucows Domains Inc.
   Registrar IANA ID: 69
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.4165350123
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   Name Server: JAY.NS.CLOUDFLARE.COM
   Name Server: LEAH.NS.CLOUDFLARE.COM
   DNSSEC: signedDelegation
   DNSSEC DS Data: 2371 13 2 AB1BD60D01D7F9503FA7355CDE4AE9A68BEB4D2AD761EAD2B98D70FD11DF8326
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T21:37:28Z <<<

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

NOTICE: The expiration date displayed in this record is the date the
registrar's sponsorship of the domain name registration in the registry is
currently set to expire. This date does not necessarily reflect the expiration
date of the domain name registrant's agreement with the sponsoring
registrar.  Users may consult the sponsoring registrar's Whois database to
view the registrar's reported date of expiration for this registration.

TERMS OF USE: You are not authorized to access or query our Whois
database through the use of electronic processes that are high-volume and
automated except as reasonably necessary to register domain names or
modify existing registrations; the Data in VeriSign Global Registry
Services' ("VeriSign") Whois database is provided by VeriSign for
information purposes only, and to assist persons in obtaining information
about or related to a domain name registration record. VeriSign does not
guarantee its accuracy. By submitting a Whois query, you agree to abide
by the following terms of use: You agree that you may use this Data only
for lawful purposes and that under no circumstances will you use this Data
to: (1) allow, enable, or otherwise support the transmission of mass
unsolicited, commercial advertising or solicitations via e-mail, telephone,
or facsimile; or (2) enable high volume, automated, electronic processes
that apply to VeriSign (or its computer systems). The compilation,
repackaging, dissemination or other use of this Data is expressly
prohibited without the prior written consent of VeriSign. You agree not to
use electronic processes that are automated and high-volume to access or
query the Whois database except as reasonably necessary to register
domain names or modify existing registrations. VeriSign reserves the right
to restrict your access to the Whois database in its sole discretion to ensure
operational stability.  VeriSign may restrict or terminate your access to the
Whois database for failure to abide by these terms of use. VeriSign
reserves the right to modify these terms at any time.

The Registry database contains ONLY .COM, .NET, .EDU domains and
Registrars.