Summary
- Registrar
- OVH
- Status
- clientTransferProhibited
- Created on
- July 25, 2024
- Expires on
- July 25, 2028
- Name servers
- jakub.ns.cloudflare.com, addyson.ns.cloudflare.com
- Mail servers
- mailserver.purelymail.com
- DMARC
- Monitoring
- SPF
- Soft
- DKIM
- No key found among the common selectors
- Website
- See the website
Spoofing protection (DMARC)
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 lain.ovh but fails SPF and DKIM checks.
- Policy
- Monitoring
- Subdomain policy
- Monitoring
- Messages covered
- 100%
- DKIM alignment
- Relaxed
- SPF alignment
- Relaxed
- Aggregate reports
- [email protected]
- Failure reports
- —
Record
v=DMARC1; p=none; rua=mailto:[email protected]
Authorized senders (SPF)
E-mails sent by any other server are accepted but flagged as suspicious.
SPF lists the servers allowed to send e-mails for lain.ovh.
| Rule | Value | Result |
|---|---|---|
| include | _spf.purelymail.com | Allowed |
| all | — | Suspicious |
Top-level DNS lookups: 1 of 10 allowed
Record
v=spf1 include:_spf.purelymail.com ~all
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 lain.ovh arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from lain.ovh 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 @lain.ovh 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
lain.ovh MX 10 mx1.lain.ovh. lain.ovh MX 20 mx2.lain.ovh.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.lain.ovh.
- 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
lain.ovh 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.lain.ovh, 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.lain.ovh 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.lain.ovh, 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.lain.ovh 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 lain.ovh
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 | 188.114.97.2 |
| A | 188.114.96.2 |
| AAAA | 2a06:98c1:3120::2 |
| AAAA | 2a06:98c1:3121::2 |
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 |
|---|---|
| jakub.ns.cloudflare.com | 108.162.195.85 |
| addyson.ns.cloudflare.com | 162.159.38.68 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @lain.ovh 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 |
|---|---|---|
| 10 | mailserver.purelymail.com | 18.204.123.63 |
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.lain.ovh.
| Name | Content |
|---|---|
| lain.ovh | 1|www.lain.ovh |
| lain.ovh | purelymail_ownership_proof=13cf4bea0d9442eace57870fdf8ec8be08845ce541c0981991584f410ace2a7a3d8ab085eb77290bc9aebc9ae317ba8b78d1c162c1b7821cf74343bca0286bd1 |
| lain.ovh | v=spf1 include:_spf.purelymail.com ~all |
| _dmarc.lain.ovh | v=DMARC1; p=none; rua=mailto:[email protected] |
Related IP addresses
IPv4 addresses used by lain.ovh: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 188.114.97.2 | Website | 188.114.97.0/24 |
| 188.114.96.2 | Website | 188.114.96.0/24 |
| 108.162.195.85 | Name server jakub.ns.cloudflare.com | 108.162.195.0/24 |
| 162.159.38.68 | Name server addyson.ns.cloudflare.com | 162.159.38.0/24 |
| 18.204.123.63 | Mail server mailserver.purelymail.com | 18.204.123.0/24 |
WHOIS of the domain lain.ovh
Domain Name: lain.ovh Registry Domain ID: DOM7957020-OVH Registrar WHOIS Server: whois.ovh.com Registrar URL: http://www.ovh.com Updated Date: 2026-07-31T15:17:21.994177Z Creation Date: 2024-07-25T06:38:22.152502Z Registry Expiry Date: 2028-07-25T06:38:22.115305Z Registrar: OVH Registrar IANA ID: 433 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +33.972101007 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Registry Registrant ID: REDACTED_FOR_PRIVACY Registrant Name: REDACTED_FOR_PRIVACY Registrant Contact Status: associated Registrant Contact Status: active Registrant Street: REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY Registrant City: REDACTED_FOR_PRIVACY Registrant Postal Code: REDACTED_FOR_PRIVACY Registrant State/Province: REDACTED_FOR_PRIVACY Registrant Country: REDACTED_FOR_PRIVACY Registrant Phone: REDACTED_FOR_PRIVACY Registrant Fax: REDACTED_FOR_PRIVACY Registrant Email: REDACTED_FOR_PRIVACY Registry Admin ID: REDACTED_FOR_PRIVACY Admin Name: REDACTED_FOR_PRIVACY Admin Contact Status: associated Admin Contact Status: active Admin Street: REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY Admin City: REDACTED_FOR_PRIVACY Admin Postal Code: REDACTED_FOR_PRIVACY Admin State/Province: REDACTED_FOR_PRIVACY Admin Country: REDACTED_FOR_PRIVACY Admin Phone: REDACTED_FOR_PRIVACY Admin Fax: REDACTED_FOR_PRIVACY Admin Email: REDACTED_FOR_PRIVACY Registry Tech ID: REDACTED_FOR_PRIVACY Tech Name: REDACTED_FOR_PRIVACY Tech Contact Status: associated Tech Contact Status: active Tech Street: REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY Tech City: REDACTED_FOR_PRIVACY Tech Postal Code: REDACTED_FOR_PRIVACY Tech State/Province: REDACTED_FOR_PRIVACY Tech Country: REDACTED_FOR_PRIVACY Tech Phone: REDACTED_FOR_PRIVACY Tech Fax: REDACTED_FOR_PRIVACY Tech Email: REDACTED_FOR_PRIVACY Registry Billing ID: REDACTED_FOR_PRIVACY Billing Name: REDACTED_FOR_PRIVACY Billing Contact Status: associated Billing Contact Status: active Billing Street: REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY, REDACTED_FOR_PRIVACY Billing City: REDACTED_FOR_PRIVACY Billing Postal Code: REDACTED_FOR_PRIVACY Billing State/Province: REDACTED_FOR_PRIVACY Billing Country: REDACTED_FOR_PRIVACY Billing Phone: REDACTED_FOR_PRIVACY Billing Fax: REDACTED_FOR_PRIVACY Billing Email: REDACTED_FOR_PRIVACY Name Server: addyson.ns.cloudflare.com Name Server: jakub.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/ >>> Last update of WHOIS database: 2026-10-02T00:50:50.588602Z <<< For more information on Whois status codes, please visit https://icann.org/epp Rights restricted by copyright. If you wish to access the protected data, please visit our website at the following address: www.nic.ovh Terms of Use : OVH SAS's database is protected by the provisions of the French Law of the 1st of July 1998 transposing the European Directive of the 11th of March 1996 on database legal protection in the Intellectual Property Code. OVH SAS is the only entity to hold the producing rights of the databases as substantial investment, quantitative as much as qualitative, that were used to achieve this database. Complete or partial reproduction and/or use of OVH SAS's database without the express permission of OVH SAS is strictly forbidden. Any breach to these rules can carry penal sanctions as counterfeit, without prejudice of a potential damages request from OVH SAS, holder of these rights. OVH SAS's database user commits to use the published data according to the laws and rules in effect. Moreover, the user is bound to respect the French Data Protection Law. The infringement of the French Data Protection Law can carry penal sanctions. As the user will access personal information, the user must refrain from collecting or misuse this information. In a more general way, the user must refrain from any act likely to infringe the privacy or reputation of individuals. Domain Name: lain.ovh Registry Domain ID: REDACTED FOR PRIVACY Registrar WHOIS Server: whois.ovh.com Registrar URL: https://ovh.com Updated Date: 2026-07-26T15:17:17Z Creation Date: 2024-07-25T06:38:22Z Registrar Registration Expiration Date: 2028-07-25T08:40:32+02:00 Registrar: OVH, SAS Registrar IANA ID: 433 Registrar Abuse Contact Email: [email protected] Registrar Abuse Contact Phone: +33.972101007 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited 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: PL 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: PL 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: PL 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: jakub.ns.cloudflare.com Name Server: addyson.ns.cloudflare.com DNSSEC: unsigned URL of the ICANN WHOIS Data Problem Reporting System: http://wdprs.internic.net/ >>> Last update of WHOIS database: 2026-07-26T15:18:25Z <<< 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-02T00:50:50Z # gmt time : 2026-10-02T00:50:50Z # last modify : 2026-07-26T15:18:25Z % Query time: 452 msec % WHEN: Fri Oct 02 00:50:50 UTC 2026