Dataweaz

adsl.cat

Summary

Registrar
OVH
Status
clientDeleteProhibited
Created on
January 30, 2022
Expires on
January 30, 2027
Name servers
maleah.ns.cloudflare.com, zeus.ns.cloudflare.com
Mail servers
mx.adsl.cat
DMARC
Reject
SPF
Soft

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 adsl.cat but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=reject; adkim=r; aspf=r

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for adsl.cat.

RuleValueResult
mx—Allowed
amx.adsl.catAllowed
ip415.204.53.84Allowed
all—Suspicious

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 mx a:mx.adsl.cat ip4:15.204.53.84 ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
dkim—RSA 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 adsl.cat arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from adsl.cat 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 @adsl.cat 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

adsl.cat  MX  10 mx1.adsl.cat.
adsl.cat  MX  20 mx2.adsl.cat.

What the record contains

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

adsl.cat  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.adsl.cat, 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.adsl.cat  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.adsl.cat, 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.adsl.cat  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 adsl.cat

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
A104.21.28.54
A172.67.144.68
AAAA2606:4700:3034::ac43:9044
AAAA2606:4700:3032::6815:1c36

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
maleah.ns.cloudflare.com172.64.34.118
zeus.ns.cloudflare.com173.245.59.249

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @adsl.cat 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
10mx.adsl.cat51.81.239.139

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.adsl.cat.

NameContent
adsl.catv=spf1 mx a:mx.adsl.cat ip4:15.204.53.84 ~all
_dmarc.adsl.catv=DMARC1; p=reject; adkim=r; aspf=r
dkim._domainkey.adsl.catv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAx5b7DTYDY6oz1HWZWc6NHH/YQ7OeCZuG2kP+ZCW/le3XAI7c6vproXydEzjdLsreffRmzKKKcJH5r03OQ3fsuhNtKQEUmJJvoNuGyXS8e+qUO+Epp6H9JPlYpnshXf1uxhHmnqEVVBohoXEqBmINW0lQ4M9vm1Qa2uCIcBbsjKqddIL2maUalN8KZuBO+pnWyfGxrKRQCWKTPpciUchatwri9mcvDlhz+Clzzh4ifnGgvM0GYIicvqNnMilYpc/ow/nsDSUzuOOAwR3e97pswH6rl44HHM72yoKowLsm8TjkEDkD0eiFQ8qR6RallaMdVQnMs2K0gH4XyN4p5aJZVwIDAQAB

Related IP addresses

IPv4 addresses used by adsl.cat: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
104.21.28.54Website104.21.28.0/24
172.67.144.68Website172.67.144.0/24
172.64.34.118Name server maleah.ns.cloudflare.com172.64.34.0/24
173.245.59.249Name server zeus.ns.cloudflare.com173.245.59.0/24
51.81.239.139Mail server mx.adsl.cat51.81.239.0/24
15.204.53.84Authorized by SPF15.204.53.0/24

WHOIS of the domain adsl.cat

Domain Name: adsl.cat
Registry Domain ID: Dgpfw263056-CAT
Registrar WHOIS Server: whois.ovh.com
Registrar URL: https://www.ovh.com
Updated Date: 2026-01-01T11:00:09.86Z
Creation Date: 2022-01-30T15:47:13.957Z
Registry Expiry Date: 2027-01-30T15:47:13.957Z
Registrar Registration Expiration Date: 
Registrar: OVH
Registrar IANA ID: 433
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +33.972101007
Reseller: 
Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Registry Registrant ID: 
Registrant Name: 
Registrant Organization: 
Registrant Street: 
Registrant City: 
Registrant State/Province: 
Registrant Postal Code: 
Registrant Country: HK
Registrant Phone: 
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: Please query the Whois service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Admin ID: 
Admin Name: 
Admin Organization: 
Admin Street: 
Admin City: 
Admin State/Province: 
Admin Postal Code: 
Admin Country: 
Admin Phone: 
Admin Phone Ext: 
Admin Fax: 
Admin Fax Ext: 
Admin Email: Please query the Whois service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Tech ID: 
Tech Name: 
Tech Organization: 
Tech Street: 
Tech City: 
Tech State/Province: 
Tech Postal Code: 
Tech Country: 
Tech Phone: 
Tech Phone Ext: 
Tech Fax: 
Tech Fax Ext: 
Tech Email: Please query the Whois service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Registry Billing ID: 
Billing Name: 
Billing Organization: 
Billing Street: 
Billing City: 
Billing State/Province: 
Billing Postal Code: 
Billing Country: 
Billing Phone: 
Billing Phone Ext: 
Billing Fax: 
Billing Fax Ext: 
Billing Email: Please query the Whois service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.
Name Server: zeus.ns.cloudflare.com
Name Server: maleah.ns.cloudflare.com
DNSSEC: signedDelegation
Canonical Name: adsl.cat
IDN Tag: ca
URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf
>>> Last update of Whois database: 2026-10-01T21:30:23.158Z <<<

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


This domain has chosen privacy settings according to the European
data protection framework provisions.

Should you need to contact the registrant, please see
http://www.domini.cat/contact-registrant

For law enforcement and trademark protection purposes, see
http://www.domini.cat/whois-access

In case of technical problems, please see
http://www.domini.cat/report-problem

Terms and Conditions of Use

The data in this record is provided by puntCAT for informational
purposes only. puntCAT does not guarantee its accuracy and cannot,
under any circumstances, be held liable in case the stored information would
prove to be wrong, incomplete or not accurate in any sense.

All the domain data that is visible in the Whois service is protected by
law. It is not permitted to use it for any purpose other than technical or
administrative requirements associated with the operation of the Internet.
It is explicitly forbidden to extract, copy and/or use or re-utilise in any
form and by any means (electronically or not) the whole or a quantitatively
or qualitatively substantial part of the contents of the Whois database
without prior and explicit written permission by puntCAT It is
prohibited, in particular, to use it for transmission of unsolicited and/or
commercial and/or advertising by phone, fax, e-mail or for any similar
purposes.

By maintaining the connection you assure that you have a legitimate interest
in the data and that you will only use it for the stated purposes. You are
aware that puntCAT maintains the right to initiate legal
proceedings against you in the event of any breach of this assurance and to
bar you from using its Whois service.

End of Whois record.
Domain Name: adsl.cat
Registry Domain ID: REDACTED FOR PRIVACY
Registrar WHOIS Server: whois.ovh.com
Registrar URL: https://ovh.com
Updated Date: 2026-01-01T11:00:09Z
Creation Date: 2022-01-30T15:47:13Z
Registrar Registration Expiration Date: 2026-01-30T16:47:17+01: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: HK
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: HK
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: HK
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: maleah.ns.cloudflare.com
Name Server: zeus.ns.cloudflare.com
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System:
http://wdprs.internic.net/
>>> Last update of WHOIS database: 2026-01-01T11:00:21Z <<<

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-01T21:30:56Z
# gmt time : 2026-10-01T21:30:56Z
# last modify : 2026-01-01T11:00:21Z

% Query time: 1049 msec
% WHEN: Thu Oct 01 21:30:55 UTC 2026