Dataweaz

thalesgroup.com

Summary

Registrar
CSC Corporate Domains, Inc.
Status
clientTransferProhibited
Created on
November 7, 2000
Expires on
November 7, 2027
Name servers
ns2.thalesgroup.com, nsa.perf1.fr, ns1.thalesgroup.com, nsc.perf1.com, nsb.perf1.com
Mail servers
mx02.thalesgroup.com, mx01.thalesgroup.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 thalesgroup.com but fails SPF and DKIM checks.

Policy
Quarantine
Subdomain policy
Quarantine
Messages covered
100%
DKIM alignment
Strict
SPF alignment
Strict
Aggregate reports
[email protected]
Failure reports
—

Record

v=DMARC1; p=quarantine; adkim=s; aspf=s; pct=100; 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 thalesgroup.com.

RuleValueResult
include_spf.thalesgroup.comAllowed
all—Rejected

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:_spf.thalesgroup.com -all

E-mail signing (DKIM)

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

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

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

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

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
ns2.thalesgroup.com192.54.145.235
nsa.perf1.fr81.92.94.100
ns1.thalesgroup.com192.54.145.234
nsc.perf1.com152.89.172.100
nsb.perf1.com81.92.95.100

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @thalesgroup.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
10mx02.thalesgroup.com23.90.122.150
10mx01.thalesgroup.com23.90.119.252

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.thalesgroup.com.

NameContent
thalesgroup.comh9pjos01vgfld5qmp5otsg8goi
thalesgroup.comstatus-page-domain-verification=6c590zq20csn
thalesgroup.comhvs9elcn2us2bmmr4lb217iqbr
thalesgroup.comonetrust-domain-verification=e84c2e4e1c404b7f89251829627370e5
thalesgroup.comatlassian-domain-verification=vLY7nBwvQAoPuK077ly9s1x3MDaKBP3iSkDrigs82hcW51Z7p5f9W78Fq/HcaGZZ
thalesgroup.comatlassian-domain-verification=QeBfwUoyAGJnMRmwGDlvGZQt9aOGErqK0xbA/Qj3WVKAwPPfn4eDvkOMsrp9MDuU
thalesgroup.comcisco-ci-domain-verification=40f4f333defc02ef6e3f607ee7bbc5dbaecd4ba7a838156e4c399ef49f8e3d5d
thalesgroup.comdtm-domain-verification=AQbpph_AlMx5E1O0tldoQc090OAPwHhr0zNaD7d15Og
thalesgroup.comsira8n255q3eerml42cnap84vq
thalesgroup.comb2cvrnha2ipmn73u2a2hslk6f4
thalesgroup.com_d49pol435n49yiy9w1qv5ne99s3lml3
thalesgroup.comgoogle-gws-recovery-domain-verification=40875700
thalesgroup.comatlassian-domain-verification=YMGUP8dtRBMsiOsafGlbeTiDEhR9qLFZftiFgRuKJ3wb21VhxZNI4gLY889nGbKh
thalesgroup.commongodb-site-verification=urJggNtlDng5wmv1jcjrXmBo9Eb0XGwN
thalesgroup.com00DE200000JCXaR=1TBE200000017Am
thalesgroup.comcisco-ci-domain-verification=7dfc7f852b0e0d4d8ee4813ed29133d2775615bbb24903c07b24aaae07fe3e0d
thalesgroup.comadobe-idp-site-verification=84253922d9f14b77c7b36641372e8c6c92f90e6ec02b32b46f25303d598dc3b4
thalesgroup.comv=spf1 include:_spf.thalesgroup.com -all
thalesgroup.comatlassian-domain-verification=rBJE2yFc7keNCJbkJbMD8pT1rBUjapGaz1gwCEY26VMJEiSW8aWaEvn9n6mggRbM
thalesgroup.comn3r0i5dfdh6s2j147759bjqc9g
thalesgroup.comcisco-ci-domain-verification=6fc601866dd489362d09d08e78445585b6e92fc640c024f864b9fca28c1b461f
thalesgroup.comstripe-verification=61B187947CCA16D0A3A2474834921E83DC33DCDA485DB744E9FC35ABE133A4D0
thalesgroup.comkiro-site-verification=1b77d56e-430c-485f-a566-795b59035692
thalesgroup.comcisco-ci-domain-verification=64495b16d25804907bea9e4ae83419db5e190204f54175c28c49bdec8eaac246
thalesgroup.com00D20000000082L=1TBUU000000021u
thalesgroup.comatlassian-domain-verification=owkhwuAcFuyTiUw4/EgbOofPLoJBM6ysS9MH1qLWXs3RAvZ14t7CSOFgh64ObH9t
thalesgroup.comatlassian-domain-verification=C8udnPAPnyatzbI4a0shdz5eVoY9BNckAvgfI99VAKwR3QiHSn4/EXa120OTZ9/Y
thalesgroup.com_1axj2rzchxezkqw0oc4gea71egqelwi
thalesgroup.com00DcX000003Yz9I=1TBcX00000004TW
thalesgroup.comparkable-domain-verification=KuSRPxVkcuVRN7997PFq7HuEKE_3Nr96aSjoHl4C-_c=
thalesgroup.comd6ckrh8i92omeb82blikqcq5oi
thalesgroup.comgoogle-gws-recovery-domain-verification=41180339
thalesgroup.com00D200000007Cr4=1TBSg00000001to
thalesgroup.comdocusign=a706bb1e-98da-4486-bf34-bc3ba14c1a42
thalesgroup.commonday-com-verification=WGu507HMpAaVXhGlx3MFTj8N_gTWVc4P169OBWSGq4w
thalesgroup.compendo-domain-verification=CF_-rQCUzGm-SYQ9PPuLhCo4B0w
thalesgroup.compardot1065712=be4c40ee770f4993ae59e60862b789b6f15b4ba4e8a2b5f22394f35dbd42c5f0
thalesgroup.combox-domain-verification=1488c4fa92053c9774352272eebca47a72f4c4f8e3dc3be8aa1ec3f60b5acbcf
thalesgroup.combox-domain-verification=acc4ffbec3edacf60e2e9e692a949a186d731f1ae02ae4b527301ec7363232c1
thalesgroup.com2d586c6048079206995c542925f5b6d6b9bd86bcb2d6500c563cb8bb29b32b07
thalesgroup.compardot128881=d94d95cd1e95d1ba52129899fa698283281594bb461c87806c0e9e5cb1de73a7
_dmarc.thalesgroup.comv=DMARC1; p=quarantine; adkim=s; aspf=s; pct=100; rua=mailto:[email protected]
selector1._domainkey.thalesgroup.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAvPHSLjSLU1VI2NRif+damCKQIFoA+OW9wJSqic3FgZ005CmvdpMklBmK780piL0ihkzO/wmFMLGvEnZ3Xl/Ci5GkVLHK+RHhGlAdPBElzJWGsP7OKN/X+ZakPKh5OpiDqWpmdfr9qJEgHP8zWHlJDQRTcTfYcucxoYyUgwu6rNDDb/B0uAQIlu002ViFalP7SqbkvnQB36P22zrxCo13dljJ0+xApWb5VpUOSqXmkEr3CVxLxsyk16gMJEZE1xbDVaYWm/Gf/2ZVxypOB+Xm4UQaZOMdNxWBv98ADos32rB0Xk+dM2g5F2/YJ+WqlpGGO+vAIRM0fgd8b3ms34VsMQIDAQAB;

Related IP addresses

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

IP addressUsed for/24 block
107.154.76.60Website107.154.76.0/24
107.154.214.60Website107.154.214.0/24
192.54.145.235Name server ns2.thalesgroup.com192.54.145.0/24
81.92.94.100Name server nsa.perf1.fr81.92.94.0/24
192.54.145.234Name server ns1.thalesgroup.com192.54.145.0/24
152.89.172.100Name server nsc.perf1.com152.89.172.0/24
81.92.95.100Name server nsb.perf1.com81.92.95.0/24
23.90.122.150Mail server mx02.thalesgroup.com23.90.122.0/24
23.90.119.252Mail server mx01.thalesgroup.com23.90.119.0/24

WHOIS of the domain thalesgroup.com

Domain Name: THALESGROUP.COM
   Registry Domain ID: 40181128_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.corporatedomains.com
   Registrar URL: http://cscdbs.com
   Updated Date: 2026-09-28T13:18:53Z
   Creation Date: 2000-11-07T11:31:23Z
   Registry Expiry Date: 2027-11-07T11:31:23Z
   Registrar: CSC Corporate Domains, Inc.
   Registrar IANA ID: 299
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: 8887802723
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: serverDeleteProhibited https://icann.org/epp#serverDeleteProhibited
   Domain Status: serverTransferProhibited https://icann.org/epp#serverTransferProhibited
   Domain Status: serverUpdateProhibited https://icann.org/epp#serverUpdateProhibited
   Name Server: NS1.THALESGROUP.COM
   Name Server: NS2.THALESGROUP.COM
   Name Server: NSA.PERF1.FR
   Name Server: NSB.PERF1.COM
   Name Server: NSC.PERF1.COM
   DNSSEC: signedDelegation
   DNSSEC DS Data: 2042 8 2 9C2A8F3074684BF3DADF624F2538FF1F0973AA7D58A707D73CF5365D54884C91
   DNSSEC DS Data: 55189 8 2 41C704003D45FC009DC73C3B96F04C5C3862C09D2FC2C71065EEFD0FEDE2C6A4
   DNSSEC DS Data: 25679 8 2 0A9DA4CA1B6FC78B4AD05C8F3E4E135D972D9F2BCEFF163C75932DD96607FB4A
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T15:50:13Z <<<

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.