Dataweaz

cp.pt

Summary

Registrar
—
Status
Registered
Created on
April 12, 1999
Expires on
May 23, 2031
Name servers
ns1.cp.pt, ns0.cp.pt
Mail servers
cp-pt.r-v1.mx.microsoft
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 cp.pt 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
[email protected]

Record

v=DMARC1; p=reject; pct=100; aspf=r; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=0;

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for cp.pt.

RuleValueResult
ip4194.65.40.88Allowed
ip4194.65.40.168Allowed
ip481.90.53.145Allowed
asmtp3.cp.ptAllowed
asmtp4.cp.ptAllowed
asmtp5.cp.ptAllowed
anewsletter.cp.ptAllowed
asmtpsrv1.cp.ptAllowed
includespf.protection.outlook.comAllowed
includespf_c.oraclecloud.comAllowed
all—Rejected

Top-level DNS lookups: 7 of 10 allowed

Record

v=spf1 ip4:194.65.40.88 ip4:194.65.40.168 ip4:81.90.53.145 a:smtp3.cp.pt a:smtp4.cp.pt a:smtp5.cp.pt a:newsletter.cp.pt a:smtpsrv1.cp.pt include:spf.protection.outlook.com include:spf_c.oraclecloud.com -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
selector1Microsoft 365RSA 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 cp.pt arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from cp.pt 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 @cp.pt 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

cp.pt  MX  10 mx1.cp.pt.
cp.pt  MX  20 mx2.cp.pt.

What the record contains

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

cp.pt  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.cp.pt, 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.cp.pt  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.cp.pt, 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.cp.pt  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 cp.pt

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
ns1.cp.pt81.90.53.140
ns0.cp.pt80.251.163.195

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @cp.pt 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
0cp-pt.r-v1.mx.microsoft52.101.68.8

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.cp.pt.

NameContent
cp.ptgoogle-site-verification=dwUBSKSaoq_iowY96k_5jFlMw9yz8XrCo8BOLFNbOG4
cp.ptv=spf1 ip4:194.65.40.88 ip4:194.65.40.168 ip4:81.90.53.145 a:smtp3.cp.pt a:smtp4.cp.pt a:smtp5.cp.pt a:newsletter.cp.pt a:smtpsrv1.cp.pt include:spf.protection.outlook.com include:spf_c.oraclecloud.com -all
cp.pt_3jt2nl9uqj0q3xknqvwcceab15urauc
_dmarc.cp.ptv=DMARC1; p=reject; pct=100; aspf=r; rua=mailto:[email protected]; ruf=mailto:[email protected]; fo=0;
selector1._domainkey.cp.ptv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDZmVxzgxhg/6lBVfBQbnih+/aODsIPeci4QElcqofTgkBgR4x3YIuMBo1pMZo6pNIwQ35dk4WO3S7LtEDqa1UkqoOght/mFwiH7ml03wbRl9b1K42VFx23zW1wkFpweldqUOk8b9ZdKgKn0IXHcBZpxuV63puCyA1Zc24DnLTviwIDAQAB; n=1024,1450846941,1466658141

Related IP addresses

IPv4 addresses used by cp.pt: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
194.65.40.120Website194.65.40.0/24
80.251.163.208Website80.251.163.0/24
81.90.53.140Name server ns1.cp.pt81.90.53.0/24
80.251.163.195Name server ns0.cp.pt80.251.163.0/24
52.101.68.8Mail server cp-pt.r-v1.mx.microsoft52.101.68.0/24
194.65.40.88Authorized by SPF194.65.40.0/24
194.65.40.168Authorized by SPF194.65.40.0/24
81.90.53.145Authorized by SPF81.90.53.0/24

WHOIS of the domain cp.pt

Domain: cp.pt
Domain Status: Registered
Creation Date: 12/04/1999 00:00:00
Expiration Date: 22/05/2031 23:59:40
Owner Name: CP - COMBOIOS DE PORTUGAL, E.P.E
Owner Address: Calçada Duque, 20
Owner Locality: Lisboa
Owner ZipCode: 1249-109
Owner Locality ZipCode: Lisboa
Owner Country Code: PT
Admin Name: CP - COMBOIOS DE PORTUGAL, E.P.E
Admin Address: Calçada Duque, 20
Admin Locality: Lisboa
Admin ZipCode: 1249-109
Admin Locality ZipCode: Lisboa
Admin Country Code: PT

Name Server: ns0.cp.pt | IPv4: 80.251.163.195 and IPv6: 
Name Server: ns1.cp.pt | IPv4: 81.90.53.140 and IPv6: 
cp.pt IN DS  13 2 31B93C60D0711935899FC3E504EFEB015EC25157BFE13111095A009C4ABF8A7A

% Query time: 832 msec
% WHEN: Fri Oct 02 18:40:16 UTC 2026