Dataweaz

knowbe4.com

Summary

Registrar
Amazon Registrar, Inc.
Status
clientTransferProhibited
Created on
August 23, 2010
Expires on
August 23, 2027
Name servers
ns-1036.awsdns-01.org, ns-1882.awsdns-43.co.uk, ns-38.awsdns-04.com, ns-853.awsdns-42.net
Mail servers
aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx4.googlemail.com, aspmx2.googlemail.com, aspmx5.googlemail.com, aspmx3.googlemail.com

Spoofing protection (DMARC)

Quarantine

E-mails spoofing this domain are sent to spam.

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

Policy
Quarantine
Subdomain policy
Quarantine
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed

Record

v=DMARC1; p=quarantine; rua=mailto:[email protected],mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected],mailto:[email protected],mailto:[email protected]; ri=3600; fo=1

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

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

RuleValueResult
includemailsenders.netsuite.comAllowed
include_spf.google.comAllowed
includemail.zendesk.comAllowed
includestspg-customer.comAllowed
ip423.21.109.212Allowed
ip423.21.109.197Allowed
ip452.49.201.246Allowed
ip452.49.235.189Allowed
ip454.172.84.90Allowed
ip4147.160.167.0/24Allowed
ip4168.235.226.71Allowed
ip4168.235.226.72Allowed
ip4168.235.226.73Allowed
ip4168.235.226.74Allowed
ip4168.235.233.211Allowed
ip4168.235.233.212Allowed
ip4168.235.233.213Allowed
ip4192.254.121.248Allowed
ip4167.89.63.53Allowed
ip4167.89.111.118Allowed
exists%{i}._spf.mta.salesforce.comAllowed
all—Rejected

Top-level DNS lookups: 5 of 10 allowed

Record

v=spf1 include:mailsenders.netsuite.com include:_spf.google.com include:mail.zendesk.com include:stspg-customer.com ip4:23.21.109.212 ip4:23.21.109.197 ip4:52.49.201.246 ip4:52.49.235.189 ip4:54.172.84.90 ip4:147.160.167.0/24 ip4:168.235.226.71 ip4:168.235.226.72 ip4:168.235.226.73 ip4:168.235.226.74 ip4:168.235.233.211 ip4:168.235.233.212 ip4:168.235.233.213  ip4:192.254.121.248 ip4:167.89.63.53 ip4:167.89.111.118 exists:%{i}._spf.mta.salesforce.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 1024 bits · shortActive
selector1Microsoft 365RSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive
default—RSA 1024 bits · shortActive
smtp—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 knowbe4.com arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from knowbe4.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 @knowbe4.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

knowbe4.com  MX  10 mx1.knowbe4.com.
knowbe4.com  MX  20 mx2.knowbe4.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.knowbe4.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

knowbe4.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.knowbe4.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.knowbe4.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.knowbe4.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.knowbe4.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 knowbe4.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.

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
ns-1036.awsdns-01.org205.251.196.12
ns-1882.awsdns-43.co.uk205.251.199.90
ns-38.awsdns-04.com205.251.192.38
ns-853.awsdns-42.net205.251.195.85

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @knowbe4.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
1aspmx.l.google.com108.177.15.27
5alt2.aspmx.l.google.com142.251.127.27
5alt1.aspmx.l.google.com192.178.213.26
10aspmx4.googlemail.com172.253.148.26
10aspmx2.googlemail.com192.178.213.27
10aspmx5.googlemail.com142.250.147.27
10aspmx3.googlemail.com142.251.127.27

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

NameContent
knowbe4.comg4l3bgqre4hkae8dfmm4v1q4je
knowbe4.comwiz-domain-verification=80d80bf3b6c164a1fd91b8150e90ba3d504058315fd7c7245a9d0f480e5f1618
knowbe4.comdocker-verification=e9e873bd-4dc8-437e-9718-93ee84b39448
knowbe4.comatlassian-domain-verification=ZhRqnN6RnH8AgFl3lYmodGh0L2aAKbEGfJETpJzak6O+lhMbMJ7WMiS392cSws63
knowbe4.commixpanel-domain-verify=bc139ab5-6f4e-41a7-b7cd-d13f89aa8710
knowbe4.comv=spf1 include:mailsenders.netsuite.com include:_spf.google.com include:mail.zendesk.com include:stspg-customer.com ip4:23.21.109.212 ip4:23.21.109.197 ip4:52.49.201.246 ip4:52.49.235.189 ip4:54.172.84.90 ip4:147.160.167.0/24 ip4:168.235.226.71 ip4:168.235.226.72 ip4:168.235.226.73 ip4:168.235.226.74 ip4:168.235.233.211 ip4:168.235.233.212 ip4:168.235.233.213 ip4:192.254.121.248 ip4:167.89.63.53 ip4:167.89.111.118 exists:%{i}._spf.mta.salesforce.com -all
knowbe4.comzapier-domain-verification-challenge=67e81d94-81d3-44c1-bb5b-f278a3ed32ca
knowbe4.combhd25m1n5fj8h8c4bchk43oeb4
knowbe4.compendo-domain-verification=02b2333b-3f4f-40ef-9659-408cec8ee1a3
knowbe4.com19e0be4ea5354278ae7eacfc48bedb9b
knowbe4.comMS=ms32168056
knowbe4.comwiz-domain-verification=e6478bb3edd119aa3e701c038708e3cb1f0f13e7691fc7b2b488592070ae6366
knowbe4.comatlassian-domain-verification=OcPNSCfFoB9IocbkPrVxgaTPH2lCVlhD1MeWq//30V3aX05otEbViZRN5iaLjPWK
knowbe4.comadobe-sign-verification=600d5d8d4ae04f20e7d625c21e96ec48
knowbe4.comamazonses:i7kVVveQqrOBBAmbA4eYXUtjyQz27rfUdUdlUdEjHjU=
knowbe4.commongodb-site-verification=CLB4dkKYnXU5G5xERSrl2N0XPr9EUX3a
knowbe4.com7bbdc96bfd404e609c241bb7a3210cc3
knowbe4.comzapier-domain-verification-challenge=f1426c5b-21d2-4bc7-82dd-e74d108c77c8
knowbe4.comanthropic-domain-verification-gcynk1=3VVkzpvdUPpZYTTCvZEyX4Ioc
knowbe4.comapple-domain-verification=qmAh14g4OX1bkue8
knowbe4.comgoogle-site-verification=EJTeC07BGnS6X2PWc5FoEbPRt8T91Y4-lhZW7RLxS-c
knowbe4.comgoogle-site-verification=WrBl38sScepa-oAzO5AlDr6qeJqHniarCDURkDMLpQs
knowbe4.comopenai-domain-verification=dv-dBBvIXDgY5ZxPl4tCjIHaNRq
knowbe4.comgoogle-site-verification=3Hie3OelJT_rJykvur3IxPN50L9mAmpstgWQu7g7rbQ
knowbe4.comjamf-site-verification=RIg8eN5i9Iok12Yr5DejHw
knowbe4.comstatus-page-domain-verification=mncmp25mgt7j
knowbe4.comadobe-idp-site-verification=370d08217eb4fd02ec25c8b9d1e4062ff87e4273d282e12f4995ea4e269c6160
knowbe4.comgoogle-site-verification=0aAUofkA6qAxk_uYttw0L4RjiIWAGL8-x-_pybvGhVo
knowbe4.comgoogle-site-verification=gzYt5XSP0eQeEkG99s_UNqSrR89qfnCg6f3uFz0v8wY
_dmarc.knowbe4.comv=DMARC1; p=quarantine; rua=mailto:[email protected],mailto:[email protected],mailto:[email protected];ruf=mailto:[email protected],mailto:[email protected],mailto:[email protected]; ri=3600; fo=1
google._domainkey.knowbe4.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCT9RLS66TdbkmlnzWSXGH5Ci6O/+CoC15GwX8XPx360pPbcCqYM/Lahl5TOKRz7mFoLdvLTOXeZ3kBr33CJPBNxVpJF3RZgdRX9JYQUfnJZ+AdfjLzef5K5Lo3ozsqB2OHxA9Sth+9DgZyQw6GL8V/0OjYH258gYqadSlVBrjQPQIDAQAB
selector1._domainkey.knowbe4.comv=DKIM1;k=rsa;p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCCKzODOkZDJsCX9XWfM+Gd9OEURivu55ljWCPYLKXrvoZW1w8o9B9DEYZa5dpA1McovxcKfTrzIciF7DSFQt2c3o0ed4LN14qyRkdyAosux7B7RvCkv0L6x8dIBFPsweCzA8/nWVFc5CX91a0Wp0XpTfheTU9lr6L2I4c7CwK0jwIDAQAB
s1._domainkey.knowbe4.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA2Fxy2gk5H4UGhn8peUWLPV0EdTEVYYl1UpI06ClpJOqfQFmHpujWsYCyke/JLXmbLCKH4YAU+0k3eB8q4bKQYSAUiliw1QnXPYvDMIJF1LCt3RyRVurrVTSJLyp304UfPuD7SFyUrA3H1RQ4mfXQPbr/ygkYX3GXUmwB2HJk0Hs6OY5s6mDW5QpR9jhw9IRbT6bvIFiLCHY5u1ogQgidyH0ceqeJ3UgIXYaRpuVXj7ONcewH1awsvjVeoA2i9NhHjdiU+BgQp3HiPh7HZhLlBETWDHXTe95EwGLxWcM5XyYUKR62ijpxJTTwnt8oOu7kLRmA73QfF2NCcrW6VqPWcwIDAQAB
s2._domainkey.knowbe4.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDg1AH8sqKi+UZxBxdZ1mcygDIiNyZRhHFrabeSHDua8OxGQs/H3tkKjxej/Ci5mvlbHnZbljaZIypbyjjImZ9ALht4EoTd5+CUslDs6JtR9FRjggZ42zMtTuWaMjIJJUC1EJbRZMt9xBT1Rs3n+040eTBMhEmP42Uy+HFGUdc3CQIDAQAB
default._domainkey.knowbe4.comv=DKIM1; g=*; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDV37ViPSDKA47nSZwc+gVo/XaLKiZeiwNSJMzyLtOie7VKjFxT/jMM7WTX2Mq//NV5ezSVWxSJh7fvdBKQJB7MWL1XK2YtCYu19fb5hS1vrd9/oyihSc0PHBplnJmeXoc4+S9nAFoKS6IUt5VF/R+IJC03xTtBnXpdtUDvCcpnaQIDAQAB
smtp._domainkey.knowbe4.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDEhgZjjqWTYAdwgbGbFybe54JOvnFkoCEzR9txYyrzRaveFE2Dvhrjrk4gzYOBLVfmTbKee72NcYIh+36iUffsaORJGWZwt52HaG0Kydxp74BeCVPZefQajKHCDa1iod7UwhOp+Z6aXitkLUmt9FS42KIt+tzV18m7+YS8oZY/hwIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
13.227.173.11Website13.227.173.0/24
13.227.173.77Website13.227.173.0/24
13.227.173.66Website13.227.173.0/24
13.227.173.63Website13.227.173.0/24
205.251.196.12Name server ns-1036.awsdns-01.org205.251.196.0/24
205.251.199.90Name server ns-1882.awsdns-43.co.uk205.251.199.0/24
205.251.192.38Name server ns-38.awsdns-04.com205.251.192.0/24
205.251.195.85Name server ns-853.awsdns-42.net205.251.195.0/24
108.177.15.27Mail server aspmx.l.google.com108.177.15.0/24
142.251.127.27Mail server alt2.aspmx.l.google.com, Mail server aspmx3.googlemail.com142.251.127.0/24
192.178.213.26Mail server alt1.aspmx.l.google.com192.178.213.0/24
172.253.148.26Mail server aspmx4.googlemail.com172.253.148.0/24
192.178.213.27Mail server aspmx2.googlemail.com192.178.213.0/24
142.250.147.27Mail server aspmx5.googlemail.com142.250.147.0/24
23.21.109.212Authorized by SPF23.21.109.0/24
23.21.109.197Authorized by SPF23.21.109.0/24
52.49.201.246Authorized by SPF52.49.201.0/24
52.49.235.189Authorized by SPF52.49.235.0/24
54.172.84.90Authorized by SPF54.172.84.0/24
168.235.226.71Authorized by SPF168.235.226.0/24
168.235.226.72Authorized by SPF168.235.226.0/24
168.235.226.73Authorized by SPF168.235.226.0/24
168.235.226.74Authorized by SPF168.235.226.0/24
168.235.233.211Authorized by SPF168.235.233.0/24
168.235.233.212Authorized by SPF168.235.233.0/24
168.235.233.213Authorized by SPF168.235.233.0/24
192.254.121.248Authorized by SPF192.254.121.0/24
167.89.63.53Authorized by SPF167.89.63.0/24
167.89.111.118Authorized by SPF167.89.111.0/24

WHOIS of the domain knowbe4.com

Domain Name: KNOWBE4.COM
   Registry Domain ID: 1612400067_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.registrar.amazon
   Registrar URL: http://registrar.amazon.com
   Updated Date: 2026-07-19T16:25:55Z
   Creation Date: 2010-08-23T16:24:14Z
   Registry Expiry Date: 2027-08-23T16:24:14Z
   Registrar: Amazon Registrar, Inc.
   Registrar IANA ID: 468
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.2024422253
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: NS-1036.AWSDNS-01.ORG
   Name Server: NS-1882.AWSDNS-43.CO.UK
   Name Server: NS-38.AWSDNS-04.COM
   Name Server: NS-853.AWSDNS-42.NET
   DNSSEC: signedDelegation
   DNSSEC DS Data: 29403 13 2 CB90BD73DC1B7A6062CB618C1963280FEF2A5D69EFDD1A8F8588608A939D9E95
   DNSSEC DS Data: 29402 13 2 95D2244BA947558E4350B951D4603C07F9CAB115956CE42B417DC636B4920DD1
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T04:32:13Z <<<

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.