metadata.cat - DNS, WHOIS, DMARC and SPF of the domain name

Summary

Registrar: 10dencehispahard S.L.U. (CDmon.com)
Status: ok
Created on: November 7, 2019
Expires on: November 7, 2026
Name servers: dns2.ilimit.net, dns1.ilimit.net, dns13.ilimit.net
Mail servers: metadata.cat
DMARC: Monitoring
SPF: Soft
DKIM: 3 keys found
Website: See the website

Spoofing protection (DMARC)

Monitoring

E-mails spoofing this domain are only reported, not blocked.

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

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

Record

v=DMARC1; p=none;

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

Rule	Value	Result
ip4	80.94.7.14	Allowed
ip4	80.94.2.132	Allowed
ip4	80.94.2.131	Allowed
ip4	79.158.33.173	Allowed
a	—	Allowed
mx	—	Allowed
include	_spf.google.com	Allowed
all	—	Suspicious

Top-level DNS lookups: 3 of 10 allowed

Record

v=spf1 ip4:80.94.7.14 ip4:80.94.2.132 ip4:80.94.2.131 ip4:79.158.33.173 +a +mx include:_spf.google.com ~all

E-mail signing (DKIM)

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

Selector	Likely service	Key	Status
k2	Mailchimp	RSA 2048 bits	Active
k3	Mailchimp	RSA 2048 bits	Active
default	—	RSA 2048 bits	Active

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

metadata.cat  MX  10 mx1.metadata.cat.
metadata.cat  MX  20 mx2.metadata.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.metadata.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

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

Type	IP address
A	80.94.7.14

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.

Server	IP address
dns2.ilimit.net	80.94.2.82
dns1.ilimit.net	136.243.238.196
dns13.ilimit.net	136.243.238.197

Mail servers (MX)

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

Priority	Server	IP address
0	metadata.cat	80.94.7.14

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

Name	Content
metadata.cat	v=spf1 ip4:80.94.7.14 ip4:80.94.2.132 ip4:80.94.2.131 ip4:79.158.33.173 +a +mx include:_spf.google.com ~all
metadata.cat	d365mktkey=Lo5UNeUngwQ1MtrPpSuwBSVpxzINLLQE05S8qOryZo8x
_dmarc.metadata.cat	v=DMARC1; p=none;
k2._domainkey.metadata.cat	v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.metadata.cat	v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
default._domainkey.metadata.cat	v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4CGMdivIhM0sm8qPMi0ExNICrVHJ8Qf3W7ddK+6UhsjlBEi9bXQmemkddCzDRVo0plLfaAHnA70DT4jEvUsgnlWfT5pxkrN4b8PuaJ65VMfQuBmjZfJ/lPjTVnbvVqusFl0kKib/jWwnKVLGAJz0WOA/JDGYyQ457QIXZ0C2Vk+KF0a7lznGzGUKspBXvr2Qcr3kMsR/JZe8PeMAJO4u0kJOv6AXurWTvTSRyrTAOUUUPP3VJemjUq7YbmZjEQ7D6KohUdt9yUu47P667KUaswCXAaJyaoQg/Yh3GkVx61zrTZeBTosTDToCIKsq6fcrwFngqjsrseqf9/u9+K8fOQIDAQAB;

Related IP addresses

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

IP address	Used for	/24 block
80.94.7.14	Website, Mail server metadata.cat, Authorized by SPF	80.94.7.0/24
80.94.2.82	Name server dns2.ilimit.net	80.94.2.0/24
136.243.238.196	Name server dns1.ilimit.net	136.243.238.0/24
136.243.238.197	Name server dns13.ilimit.net	136.243.238.0/24
80.94.2.132	Authorized by SPF	80.94.2.0/24
80.94.2.131	Authorized by SPF	80.94.2.0/24
79.158.33.173	Authorized by SPF	79.158.33.0/24

WHOIS of the domain metadata.cat

Domain Name: metadata.cat
Registry Domain ID: Dpash217520-CAT
Registrar WHOIS Server: whois.cdmon.com
Registrar URL: https://www.cdmon.com
Updated Date: 2025-10-24T02:30:14.384Z
Creation Date: 2019-11-07T11:15:48.11Z
Registry Expiry Date: 2026-11-07T11:15:48.11Z
Registrar Registration Expiration Date: 
Registrar: 10dencehispahard S.L.U. (CDmon.com)
Registrar IANA ID: 1403
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +34.935677577
Reseller: 
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: 
Registrant Name: 
Registrant Organization: 
Registrant Street: 
Registrant City: 
Registrant State/Province: Barcelona
Registrant Postal Code: 
Registrant Country: ES
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: ns1.tirabol.cat
Name Server: ns2.tirabol.cat
DNSSEC: unsigned
Canonical Name: metadata.cat
IDN Tag: ca
URL of the ICANN Whois Inaccuracy Complaint Form: https://icann.org/wicf
>>> Last update of Whois database: 2026-10-02T16:48:56.163Z <<<

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: METADATA.CAT
Registry Domain ID: 
Registrar WHOIS Server: whois.cdmon.com
Registrar URL: https://www.cdmon.com
Updated Date: 2020-03-23T12:35:28Z
Creation Date: 2019-11-07T11:15:48Z
Registrar Registration Expiration Date: 2026-11-07T11:15:48Z
Registrar: 10DENCEHISPAHARD, S.L
Registrar IANA ID: 1403
Registrar Abuse Contact Email: [email protected]
Registrar Abuse Contact Phone: +34.935677577
Domain Status: ok https://icann.org/epp#ok
Registry Registrant ID: 
Registrant Name: 
Registrant Organization: FUNDACIO CERCLE TECNOLOGIC DE CATALUNYA
Registrant Street: 
Registrant City: 
Registrant State/Province: Barcelona
Registrant Postal Code: 
Registrant Country: ES
Registrant Phone: 
Registrant Phone Ext: 
Registrant Fax: 
Registrant Fax Ext: 
Registrant Email: http://www.whoiscontactsprotection.com/
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: http://www.whoiscontactsprotection.com/
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: http://www.whoiscontactsprotection.com/
Name Server: ns1.tirabol.cat
Name Server: ns2.tirabol.cat
DNSSEC: unsigned
URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/
>>> Last update of whois database: 2026-10-02T18:49:45+0200 <<<

For more information on Whois status codes, please visit https://www.icann.org/resources/pages/epp-status-codes-2014-06-16-en


The information in this whois database is provided for the sole purpose 
of assisting you in obtaining information about domain name registration records.
This information is available "as is," and we do not guarantee its accuracy.
By submitting a whois query, you agree that you will use this data only for
lawful purposes and that, under no circumstances will you use this data to: (1)
enable high volume, automated, electronic processes that stress or load this whois
database system providing you this information; or (2) allow, enable, or otherwise
support the transmission of mass, unsolicited, commercial advertising or solicitations
via facsimile, electronic mail, or by telephone to entities other than your own existing
customers.  The compilation, repackaging, dissemination or other use of this data
is expressly prohibited without prior written consent from 10Dencehispahard SL.


10Dencehispahard SL reserves the right to modify these terms at any
time. By submitting an inquiry, you agree to these terms of usage
and limitations of warranty.

% Query time: 1036 msec
% WHEN: Fri Oct 02 16:49:44 UTC 2026