Dataweaz

bouncer.cloud

Summary

Registrar
Gandi SAS
Status
clientTransferProhibited
Created on
September 24, 2018
Expires on
September 24, 2027
Name servers
ns-1758.awsdns-27.co.uk, ns-729.awsdns-27.net, ns-1197.awsdns-21.org, ns-387.awsdns-48.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 bouncer.cloud 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
—

Record

v=DMARC1; p=reject; rua=mailto:[email protected];

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for bouncer.cloud.

RuleValueResult
mx—Allowed
ip451.89.142.0/24Allowed
ip4193.70.63.0/24Allowed
ip451.77.180.0/24Allowed
ip451.77.111.198Allowed
ip4146.70.153.0/24Allowed
all—Rejected

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 mx ip4:51.89.142.0/24 ip4:193.70.63.0/24 ip4:51.77.180.0/24 ip4:51.77.111.198 ip4:146.70.153.0/24 -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive

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

bouncer.cloud  MX  10 mx1.bouncer.cloud.
bouncer.cloud  MX  20 mx2.bouncer.cloud.

What the record contains

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

bouncer.cloud  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.bouncer.cloud, 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.bouncer.cloud  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.bouncer.cloud, 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.bouncer.cloud  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 bouncer.cloud

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-1758.awsdns-27.co.uk205.251.198.222
ns-729.awsdns-27.net205.251.194.217
ns-1197.awsdns-21.org205.251.196.173
ns-387.awsdns-48.com205.251.193.131

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @bouncer.cloud 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.com64.233.184.26
5alt2.aspmx.l.google.com142.251.127.26
5alt1.aspmx.l.google.com192.178.213.27
10aspmx2.googlemail.com192.178.213.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.bouncer.cloud.

NameContent
bouncer.cloudv=spf1 mx ip4:51.89.142.0/24 ip4:193.70.63.0/24 ip4:51.77.180.0/24 ip4:51.77.111.198 ip4:146.70.153.0/24 -all
_dmarc.bouncer.cloudv=DMARC1; p=reject; rua=mailto:[email protected];
google._domainkey.bouncer.cloudv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAoaldqa0cCYGvbWgVR4VCzBW3/FYxPptgGLxMl4DkszxfhDbsDeTIAfqxBaLbHMbn37ka50Ljpz5I+YmDpplXd5fltiKrvd6GwwsaEtCCc24HK8xKRtBKAx5aKZ0Drpum6sZC21oWciP7SzfgmspFxDKFgNOn8wI2EbprY0b2AKhHnP+GKgogEhaGnu5N0Sfaqpgune8LqsyjKR2phBDK9r/ZNl4jlfZTO0GwEJTK8FUTwyCZqyLmoV19j3iUqGcZnneiiZpTm4UP0DPvpsfdfUtgE4n/S353foufoawfotbqfU2UMc5/52Hmv0V0Ii3PttqP5oVrWvqfWh3fivhcRwIDAQAB

Related IP addresses

IPv4 addresses used by bouncer.cloud: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
13.249.228.125Website13.249.228.0/24
13.249.228.21Website13.249.228.0/24
13.249.228.12Website13.249.228.0/24
13.249.228.71Website13.249.228.0/24
205.251.198.222Name server ns-1758.awsdns-27.co.uk205.251.198.0/24
205.251.194.217Name server ns-729.awsdns-27.net205.251.194.0/24
205.251.196.173Name server ns-1197.awsdns-21.org205.251.196.0/24
205.251.193.131Name server ns-387.awsdns-48.com205.251.193.0/24
64.233.184.26Mail server aspmx.l.google.com64.233.184.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
51.77.111.198Authorized by SPF51.77.111.0/24

WHOIS of the domain bouncer.cloud

Domain Name: bouncer.cloud
Registry Domain ID: D86604B797C1B49C2B1F1C6C5ED806AD9-NSR
Registrar WHOIS Server: whois.gandi.net
Registrar URL: www.gandi.net
Updated Date: 2026-08-25T13:30:28.114Z
Creation Date: 2018-09-24T13:24:32.395Z
Registry Expiry Date: 2027-09-24T13:24:32.395Z
Registrar: Gandi SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: 
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Name Server: ns-387.awsdns-48.com
Name Server: ns-1758.awsdns-27.co.uk
Name Server: ns-729.awsdns-27.net
Name Server: ns-1197.awsdns-21.org
DNSSEC: unsigned
URL of the ICANN RDDS Inaccuracy Complaint Form: https://icann.org/wicf

>>> Last update of WHOIS database: 2026-10-01T04:40:45.755Z <<<

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

The WHOIS information provided in this page has been redacted
in compliance with ICANN's Temporary Specification for gTLD
Registration Data.

The data in this record is provided by Tucows Registry for informational
purposes only, and it does not guarantee its accuracy. Tucows Registry is
authoritative for whois information in top-level domains it operates
under contract with the Internet Corporation for Assigned Names and
Numbers. Whois information from other top-level domains is provided by
a third-party under license to Tucows Registry.

This service is intended only for query-based access. By using this
service, you agree that you will use any data presented only for lawful
purposes and that, under no circumstances will you use (a) data
acquired for the purpose of allowing, enabling, or otherwise supporting
the transmission by e-mail, telephone, facsimile or other
communications mechanism of mass  unsolicited, commercial advertising
or solicitations to entities other than your existing  customers; or
(b) this service to enable high volume, automated, electronic processes
that send queries or data to the systems of any Registrar or any
Registry except as reasonably necessary to register domain names or
modify existing domain name registrations.

Tucows Registry reserves the right to modify these terms at any time. By
submitting this query, you agree to abide by this policy. All rights
reserved.
Domain Name: bouncer.cloud
Registry Domain ID: D86604B797C1B49C2B1F1C6C5ED806AD9-NSR
Registrar WHOIS Server: whois.gandi.net
Registrar URL: http://www.gandi.net
Updated Date: 2026-08-20T13:33:08Z
Creation Date: 2018-09-24T11:24:32Z
Registrar Registration Expiration Date: 2027-09-24T13:24:32Z
Registrar: GANDI SAS
Registrar IANA ID: 81
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.170377661
Reseller: Amazon Registrar, Inc.
Domain Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
Domain Status: 
Domain Status: 
Domain Status: 
Domain Status: 
Registry Registrant ID: REDACTED FOR PRIVACY
Registrant Name: REDACTED FOR PRIVACY
Registrant Organization: Bouncer Sp. z o.o.
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province: 
Registrant Postal Code: REDACTED FOR PRIVACY
Registrant Country: PL
Registrant Phone: REDACTED FOR PRIVACY
Registrant Phone Ext:
Registrant Fax: REDACTED FOR PRIVACY
Registrant Fax Ext:
Registrant Email: [email protected]
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: REDACTED FOR PRIVACY
Admin Phone: REDACTED FOR PRIVACY
Admin Phone Ext:
Admin Fax: REDACTED FOR PRIVACY
Admin Fax Ext:
Admin Email: [email protected]
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: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext:
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext:
Tech Email: [email protected]
Name Server: NS-1197.AWSDNS-21.ORG
Name Server: NS-729.AWSDNS-27.NET
Name Server: NS-1758.AWSDNS-27.CO.UK
Name Server: NS-387.AWSDNS-48.COM
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
Name Server: 
DNSSEC: Unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-10-01T04:40:45Z <<<

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

Reseller Email: 
Reseller URL: 

Personal data access and use are governed by French law, any use for the purpose of unsolicited mass commercial advertising as well as any mass or automated inquiries (for any intent other than the registration or modification of a domain name) are strictly forbidden. Copy of whole or part of our database without Gandi's endorsement is strictly forbidden.
A dispute over the ownership of a domain name may be subject to the alternate procedure established by the Registry in question or brought before the courts.
For additional information, please contact us via the following form:
 https://www.gandi.net/support/contacter/mail/

% Query time: 640 msec
% WHEN: Thu Oct 01 04:40:45 UTC 2026