Dataweaz

unbounce.com

Summary

Registrar
NameCheap, Inc.
Status
clientTransferProhibited
Created on
July 19, 2009
Expires on
July 19, 2027
Name servers
ns-51.awsdns-06.com, ns-832.awsdns-40.net, ns-1035.awsdns-01.org, ns-1873.awsdns-42.co.uk
Mail servers
aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, aspmx3.googlemail.com, aspmx2.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 unbounce.com but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=quarantine; rua=mailto:[email protected],mailto:[email protected];  pct=100;

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

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

RuleValueResult
includeUniversalSPF.orgAllowed
includex.UniversalSPF.orgRejected
include_spf.salesforce.comAllowed
include_spf.google.comAllowed
includesendgrid.netAllowed
includemail.zendesk.comAllowed
includespf.mail.intercom.ioAllowed
includeet._spf.pardot.comAllowed
includecust-spf.exacttarget.comAllowed
includespf.mandrillapp.comAllowed
all—Rejected

Top-level DNS lookups: 10 of 10 allowed

Record

v=spf1 include:UniversalSPF.org -include:x.UniversalSPF.org include:_spf.salesforce.com include:_spf.google.com include:sendgrid.net include:mail.zendesk.com include:spf.mail.intercom.io include:et._spf.pardot.com include:cust-spf.exacttarget.com include:spf.mandrillapp.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 1024 bits · shortActive
k1MailchimpRSA 1024 bits · shortActive
mandrillMandrillRSA 1024 bits · shortActive
s1SendGridRSA 2048 bitsActive
s2SendGridRSA 2048 bitsActive
zendesk1ZendeskRSA 2048 bitsActive
zendesk2ZendeskRSA 2048 bitsActive

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

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

unbounce.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.unbounce.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.unbounce.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.unbounce.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.unbounce.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 unbounce.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
A162.159.134.42

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-51.awsdns-06.com205.251.192.51
ns-832.awsdns-40.net205.251.195.64
ns-1035.awsdns-01.org205.251.196.11
ns-1873.awsdns-42.co.uk205.251.199.81

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @unbounce.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.com66.102.1.26
20alt2.aspmx.l.google.com142.251.127.26
20alt1.aspmx.l.google.com192.178.213.27
30aspmx3.googlemail.com142.251.127.27
30aspmx2.googlemail.com192.178.213.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.unbounce.com.

NameContent
unbounce.comanthropic-domain-verification-krvjyy=NvZWkvQO5cDBbglszJ5V7YAwT
unbounce.comatlassian-domain-verification=Up9207DREL/RgUcKcUtgnnwhGMxMrI00VRjgARh7Q/48gnYwPMn+NdvRUf3OSVpQ
unbounce.comca3-e174523301e14f6a8b3dac1026c9885d
unbounce.comca3-f16a6f69c37343948bb56a2c695bfce0
unbounce.comcursor-domain-verification-b59b82=V38RSuDZZfZQO6tzOwNkw7I5X
unbounce.comgoogle-site-verification=B7zG78T7i_lrr6zN26cazM5UywNYz2Xc2WxUugXhX_A
unbounce.comgoogle-site-verification=Kds1iesXSU-TNnBua16D9X-y916pWueJlTWzSgQsETE
unbounce.comgoogle-site-verification=MCkbe05xY48Vy94A7vLuA625FJFw1GNwOabik2Wbyu4
unbounce.comgoogle-site-verification=loMDx1ITrY_H9iRm-HxXCGIyGJLR87pbzlfhWGdKfOA
unbounce.comgoogle-site-verification=vsdc0xp8BrpyO50V1LUWDP30Qbn6F4Un3KsWmjJW_lE
unbounce.comgoogle-site-verification=xBmPNwOG2j0s72PewstviPH6AE8CL-nYkUIjmzKCjes
unbounce.comhubspot-developer-verification=ZWJlYjhjM2ItZjA1ZS00MmNlLWEyYzktZmRkZTk5NzRiMDc3
unbounce.comjamf-site-verification=lQMiOFm3x67gyJyyKHfxoA
unbounce.commiro-verification=e16daa353bd2bcf88f002195fc7af9c504b68642
unbounce.commixpanel-domain-verify=2901363a-bc43-4bfb-937d-aba8371a666d
unbounce.comnotion-domain-verification=3vhNxK5TMvMqHHYGc4BoXK9sk1fiwJSqergOazsA2Ex
unbounce.compardot405592=11cb0d3100e5a319629b598665bfa6b1ddaa5ebc56a97e8b6a1123dfd63d8494
unbounce.compendo-domain-verification=vqluVl4jFhPeZyJxZZgsiDCi918
unbounce.comremote-domain-verification=2f18ba1b-3420-4ccf-a3a7-84ca02580923
unbounce.comrillet-domain-verification-4ywdm9=qqaNMJupFNErqtQ2zkL436agY
unbounce.comrillet-domain-verification-fxcf2b=ITKwCrFyz00CDOKjV5arE5qkU
unbounce.comstripe-verification=69EF7D7CE26F1B15388A9E877C17ADD9503E2A427FDBC56D2788ACE06F4C9327
unbounce.comv=spf1 include:UniversalSPF.org -include:x.UniversalSPF.org include:_spf.salesforce.com include:_spf.google.com include:sendgrid.net include:mail.zendesk.com include:spf.mail.intercom.io include:et._spf.pardot.com include:cust-spf.exacttarget.com include:spf.mandrillapp.com -all
unbounce.comZOOM_verify_bZGQtIE0cOjNQo6WNMwN8q
_dmarc.unbounce.comv=DMARC1; p=quarantine; rua=mailto:[email protected],mailto:[email protected]; pct=100;
google._domainkey.unbounce.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC11cPz7V8q8cxcnFsu4P32GFnDLgeDN10jxNL+KBrAaUInMBVHyyMJckAv4qD1mg0MFI0CChkDhScwtH0oajvstWQsh2S22CJg2Ngd0QyOFAsdBDkvWdCpqWyGHz0iG54G4wyjKv1dpCrczh/P7mPfJgJqY5kVSS62OAyhAApVxQIDAQAB
k1._domainkey.unbounce.comk=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDbNrX2cY/GUKIFx2G/1I00ftdAj713WP9AQ1xir85i89sA2guU0ta4UX1Xzm06XIU6iBP41VwmPwBGRNofhBVR+e6WHUoNyIR4Bn84LVcfZE20rmDeXQblIupNWBqLXM1Q+VieI/eZu/7k9/vOkLSaQQdml4Cv8lb3PcnluMVIhQIDAQAB;
mandrill._domainkey.unbounce.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;
s1._domainkey.unbounce.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAugz0MUrg1w4Itj68kNiXEAaFJQbsd+3liYBdxwliRuUEttuMYr6r9Tcc/AqxkPkrz7Xtp7ujiZ+8K4pirTo5Y90AIvw9RcgR3k7tx5qcgWPObSAXDXnUhec9VkfHu8b8y+8Z+KQwK+gmdegR+MMi/hXOxBtWN1Z3/xPuaBQfRNyHPzkQMeZEc2NJPL0nWdqdWpmcVued1iZVHnKoCTFnOLvy8IGX4TcwTtZxTWJWzAptA44z6TMERi1xWZv5pucewTfqaOZ5tVdOb/8IxowNVPZ8+yJRdT7Z/62lPmcZVtlll2T3OXbUCvmKarhlhwHa9t88TVP1QBlKV4NHqYJ4TwIDAQAB
s2._domainkey.unbounce.comk=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAqv+HvKbynuhlk/Io0MqihZdQvb2FU9KKB9BIMcSSHSzPBcZwP29tuJy9C1I5ucAPBbK+0ZpuCPaHUxH/3A1eRPnhv+144V2G1onR6peyj4mdwRCXdLCV1Q/2HMBFZCTX4Ievee4eWW61YScsk3N2iVFMc+eO+eOwmCC6RlmQlm5V3/ATuKIore4RvqM/xK0gFQ8DQeGDy1ukj3Dtl1wlGq8g+N3fAaWnkvt0hL0tUjam/KAAQQ4fYHQzvHUIkYjh3iAzOIHL8qMTe3pnrWdeUkLhqTt4s4toxunFfMhNK+caqMtlep4FC1UdcsTCOLkB9/5IgGhCasRXRMk2W0+E/QIDAQAB
zendesk1._domainkey.unbounce.comv=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey.unbounce.comv=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
162.159.134.42Website162.159.134.0/24
205.251.192.51Name server ns-51.awsdns-06.com205.251.192.0/24
205.251.195.64Name server ns-832.awsdns-40.net205.251.195.0/24
205.251.196.11Name server ns-1035.awsdns-01.org205.251.196.0/24
205.251.199.81Name server ns-1873.awsdns-42.co.uk205.251.199.0/24
66.102.1.26Mail server aspmx.l.google.com66.102.1.0/24
142.251.127.26Mail server alt2.aspmx.l.google.com142.251.127.0/24
192.178.213.27Mail server alt1.aspmx.l.google.com, Mail server aspmx2.googlemail.com192.178.213.0/24
142.251.127.27Mail server aspmx3.googlemail.com142.251.127.0/24

WHOIS of the domain unbounce.com

Domain Name: UNBOUNCE.COM
   Registry Domain ID: 1562859644_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.namecheap.com
   Registrar URL: http://www.namecheap.com
   Updated Date: 2026-06-19T10:41:40Z
   Creation Date: 2009-07-19T14:12:02Z
   Registry Expiry Date: 2027-07-19T14:12:02Z
   Registrar: NameCheap, Inc.
   Registrar IANA ID: 1068
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.6613102107
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Name Server: NS-1035.AWSDNS-01.ORG
   Name Server: NS-1873.AWSDNS-42.CO.UK
   Name Server: NS-51.AWSDNS-06.COM
   Name Server: NS-832.AWSDNS-40.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-02T17:47:43Z <<<

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.