Dataweaz

matsu.design

Summary

Registrar
OVH sas
Status
clientTransferProhibited
Created on
January 6, 2024
Expires on
January 6, 2027
Name servers
dns102.ovh.net, ns102.ovh.net
Mail servers
mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net
SPF
Strict
DKIM
No key found among the common selectors
Website
See the website

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

SPF lists the servers allowed to send e-mails for matsu.design.

RuleValueResult
includemx.ovh.comAllowed
all—Rejected

Top-level DNS lookups: 1 of 10 allowed

Record

v=spf1 include:mx.ovh.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 matsu.design arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from matsu.design 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 @matsu.design 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

matsu.design  MX  10 mx1.matsu.design.
matsu.design  MX  20 mx2.matsu.design.

What the record contains

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

matsu.design  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.matsu.design, 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.matsu.design  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.matsu.design, 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.matsu.design  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 matsu.design

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
A216.150.1.1

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
dns102.ovh.net5.196.38.181
ns102.ovh.net5.135.54.1

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @matsu.design 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
1mx1.mail.ovh.net188.165.36.237
5mx2.mail.ovh.net87.98.160.167
100mx3.mail.ovh.net91.121.53.175

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.matsu.design.

NameContent
matsu.designv=spf1 include:mx.ovh.com -all

Related IP addresses

IPv4 addresses used by matsu.design: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
216.150.1.1Website216.150.1.0/24
5.196.38.181Name server dns102.ovh.net5.196.38.0/24
5.135.54.1Name server ns102.ovh.net5.135.54.0/24
188.165.36.237Mail server mx1.mail.ovh.net188.165.36.0/24
87.98.160.167Mail server mx2.mail.ovh.net87.98.160.0/24
91.121.53.175Mail server mx3.mail.ovh.net91.121.53.0/24

WHOIS of the domain matsu.design

Domain Name: matsu.design
Registry Domain ID: REDACTED FOR PRIVACY
Registrar WHOIS Server: whois.ovh.com
Registrar URL: www.ovh.com
Updated Date: 2026-02-20T13:30:14Z
Creation Date: 2024-01-06T13:30:11Z
Registry Expiry Date: 2027-01-06T13:30:11Z
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: Mateusz Wierzbicki
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant Street: REDACTED FOR PRIVACY
Registrant City: REDACTED FOR PRIVACY
Registrant State/Province:
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: Please query the RDDS 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 Street:
Admin Street:
Admin City:
Admin State/Province:
Admin Postal Code:
Admin Country:
Admin Phone:
Admin Phone Ext:
Admin Fax:
Admin Fax Ext:
Admin Email:
Registry Tech ID: REDACTED FOR PRIVACY
Tech Name: REDACTED FOR PRIVACY
Tech Organization: REDACTED FOR PRIVACY
Tech Street: REDACTED FOR PRIVACY
Tech Street: 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: REDACTED FOR PRIVACY
Tech Phone: REDACTED FOR PRIVACY
Tech Phone Ext: REDACTED FOR PRIVACY
Tech Fax: REDACTED FOR PRIVACY
Tech Fax Ext: REDACTED FOR PRIVACY
Tech Email: Please query the RDDS 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: dns102.ovh.net
Name Server: ns102.ovh.net
DNSSEC: signedDelegation
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2026-10-02T17:10:59Z <<<

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

The Service is provided so that you may look up certain information in relation to domain names that we store in our database.

Use of the Service is subject to our policies, in particular you should familiarise yourself with our Acceptable Use Policy and our Privacy Policy.

The information provided by this Service is 'as is' and we make no guarantee of it its accuracy.

You agree that by your use of the Service you will not use the information provided by us in a way which is:
* inconsistent with any applicable laws,
* inconsistent with any policy issued by us,
* to generate, distribute, or facilitate unsolicited mass email, promotions, advertisings or other solicitations, or
* to enable high volume, automated, electronic processes that apply to the Service.

You acknowledge that:
* a response from the Service that a domain name is 'available', does not guarantee that is able to be registered,
* we may restrict, suspend or terminate your access to the Service at any time, and
* the copying, compilation, repackaging, dissemination or other use of the information provided by the Service is not permitted, without our express written consent.

This information has been prepared and published in order to represent administrative and technical management of the TLD.

We may discontinue or amend any part or the whole of these Terms of Service from time to time at our absolute discretion.
Domain Name: matsu.design
Registry Domain ID: REDACTED FOR PRIVACY
Registrar WHOIS Server: whois.ovh.com
Registrar URL: https://ovh.com
Updated Date: 2025-12-01T15:01:24Z
Creation Date: 2024-01-06T13:30:11Z
Registrar Registration Expiration Date: 2027-01-06T14:32:24+01: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: dns102.ovh.net
Name Server: ns102.ovh.net
DNSSEC: signedDelegation
URL of the ICANN WHOIS Data Problem Reporting System:
http://wdprs.internic.net/
>>> Last update of WHOIS database: 2025-12-29T12:11:37Z <<<

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-02T17:10:59Z
# gmt time : 2026-10-02T17:10:59Z
# last modify : 2025-12-29T12:11:37Z

% Query time: 885 msec
% WHEN: Fri Oct 02 17:10:58 UTC 2026