Summary
- Registrar
- GoDaddy.com
- Status
- Arizona
- Created on
- November 14, 2018
- Expires on
- November 14, 2026
- Name servers
- hank.ns.cloudflare.com, elle.ns.cloudflare.com
- Mail servers
- aspmx.l.google.com, alt2.aspmx.l.google.com, alt1.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com
- DMARC
- Reject
- SPF
- Soft
- DKIM
- 3 keys found
- Website
- See the website
Spoofing protection (DMARC)
E-mails spoofing this domain are rejected.
DMARC tells mail servers what to do with an e-mail that claims to come from justo.mx but fails SPF and DKIM checks.
- Policy
- Reject
- Subdomain policy
- Reject
- Messages covered
- 50%
- DKIM alignment
- Relaxed
- SPF alignment
- Relaxed
- Aggregate reports
- [email protected]
- Failure reports
- [email protected]
Record
v=DMARC1; p=reject; pct=50; fo=1; rua=mailto:[email protected]; ruf=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 justo.mx.
| Rule | Value | Result |
|---|---|---|
| mx | — | Allowed |
| include | spf.autopilothq.com | Allowed |
| include | sendgrid.net | Allowed |
| include | _spf.google.com | Allowed |
| include | mail.zendesk.com | Allowed |
| all | — | Suspicious |
Top-level DNS lookups: 5 of 10 allowed
Record
v=spf1 mx include:spf.autopilothq.com include:sendgrid.net include:_spf.google.com include:mail.zendesk.com ~all
E-mail signing (DKIM)
DKIM keys published by justo.mx under the most common selectors. Other keys may exist under selectors specific to each sending service.
| Selector | Likely service | Key | Status |
|---|---|---|---|
| Google Workspace | RSA 2048 bits | Active | |
| s1 | SendGrid | RSA 2048 bits | Active |
| s2 | SendGrid | RSA 1024 bits · short | Active |
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 justo.mx arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from justo.mx 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 @justo.mx 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
justo.mx MX 10 mx1.justo.mx. justo.mx MX 20 mx2.justo.mx.
What the record contains
- 10, 20
- Priority: the server with the lowest number is tried first. Servers with equal priority share the load.
- mx1.justo.mx.
- 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
justo.mx 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.justo.mx, 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.justo.mx 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.justo.mx, 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.justo.mx 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 justo.mx
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 | 172.66.168.97 |
| A | 104.20.22.192 |
| AAAA | 2606:4700:10::ac42:a861 |
| AAAA | 2606:4700:10::6814:16c0 |
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 |
|---|---|
| hank.ns.cloudflare.com | 108.162.193.116 |
| elle.ns.cloudflare.com | 173.245.58.110 |
Mail servers (MX)
MX records point to the servers that receive e-mails sent to the domain, that is to @justo.mx 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 |
|---|---|---|
| 1 | aspmx.l.google.com | 66.102.1.27 |
| 5 | alt2.aspmx.l.google.com | 142.251.127.26 |
| 5 | alt1.aspmx.l.google.com | 192.178.213.27 |
| 10 | alt3.aspmx.l.google.com | 172.253.148.27 |
| 10 | alt4.aspmx.l.google.com | 142.250.147.27 |
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.justo.mx.
| Name | Content |
|---|---|
| justo.mx | mixpanel-domain-verify=4949b8fa-81ab-4093-9a8c-7c17ced772b6 |
| justo.mx | new-relic-domain-verification=c8ad498eaf854674ba3b4cad378b7399 |
| justo.mx | v=spf1 mx include:spf.autopilothq.com include:sendgrid.net include:_spf.google.com include:mail.zendesk.com ~all |
| justo.mx | MS=ms60476914 |
| justo.mx | facebook-domain-verification=5ufn08zxu4rlm12xf8enrs5oge4usi |
| justo.mx | google-site-verification=1NEdwYTIq1y7zCx0xWsUZFvZu9AV8V5xPPtO_dC6UoU |
| justo.mx | google-site-verification=V0lnrHwPqhHxGfBSq94ZPtbGmLfj8B6t-nZ81xypq34 |
| justo.mx | google-site-verification=iBxBq6Gg-S6TMniRJsJP2r4nYvMjaevCV-eD0QG0R94 |
| justo.mx | google-site-verification=o6h-9Bf05b7LrtLonJWwQgAyOLSG6KcdecipDUVMmJk |
| justo.mx | heritage=external-dns,external-dns/owner=justo.mx,justo.cloud,external-dns/resource=ingress/default/justo-dashboard |
| justo.mx | heritage=external-dns,external-dns/owner=justo.mx,justo.cloud,external-dns/resource=ingress/default/justo-web |
| justo.mx | heritage=external-dns,external-dns/owner=justo.mx,justo.cloud,external-dns/resource=ingress/default/justo-web-ddos |
| _dmarc.justo.mx | v=DMARC1; p=reject; pct=50; fo=1; rua=mailto:[email protected]; ruf=mailto:[email protected] |
| google._domainkey.justo.mx | v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmJ5/T5Vx7HjrFKZ4NN49l/M6eYTFDncf1qideyVXX5rSE7LRxgpPL3eupM2x43eBD4xMrn/vW/l6PGuN5WA902BNtlJfUPNMLhHFzEvCoJxcGV+SA8gzphRpicU0c4jfvs9iVgiyuAGOeYpyzRRV6b4sCrHQeeM48A3JM3P5jm5Vpa37ho4NEPibyq35Hyumc6zmHwZiiMoQGMZSMIsFbFsIOxWAft12LSI9KcT4G6i6RhjTapRZaW6ll6+5j8/DaDbMKrQMbeYEqYMfzbRADRl1pDWrfh9NHQjmi7jJIvMrUQffDhfMI7CVipfONGooh4+zLLYYnq/vIK0VsxS4IQIDAQAB |
| s1._domainkey.justo.mx | k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4xrjLJJPV4OFY/vJtWqZ+53o7N9P2iT8ULKLyOAbEZYVxZDF/64IGZWlzQAcP3vfku+B9cJVTo010ToALR5xB7jKX8PFI55ZX5/BqDh3YVnzo0dDGym4vHurCfZ7LsTEHpJy7jOZUgfaXSRl4fkYrvGRiQ5c8kcAhwEysTvsXvUZVtEXap+d9wmG+smLs+hIxyEsBkJC9JrazrM27vO7tWja+B9wW+ln27hoQ561L12j+V6UUM1/uTzhhvekrhVnj9YfhXqlHPZHcjWq7QnaA8Kr0VxrjDxxe4eJfXlATHv2V/0YgL+1RI7kVoAC/N/1hSJGLrjMqC5ZjlAKFOQkvwIDAQAB |
| s2._domainkey.justo.mx | k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCiFWcu5affpxGAxLtuyesvFhYxRV032Xh1TbfMjmj6ZQnc2DrjuPNICJDhI68visRdLo0qn4WDm2mNecV5F6dB/sc5+N6IPhT4GVooavHNhk+BSOXMckUu27ZQn3RPSzDdrdU8X9M17LcJrsEuXw8yL2x9mkeVze2izKkurJuDJQIDAQAB |
Related IP addresses
IPv4 addresses used by justo.mx: website, name servers, mail servers and senders authorized by SPF.
| IP address | Used for | /24 block |
|---|---|---|
| 172.66.168.97 | Website | 172.66.168.0/24 |
| 104.20.22.192 | Website | 104.20.22.0/24 |
| 108.162.193.116 | Name server hank.ns.cloudflare.com | 108.162.193.0/24 |
| 173.245.58.110 | Name server elle.ns.cloudflare.com | 173.245.58.0/24 |
| 66.102.1.27 | Mail server aspmx.l.google.com | 66.102.1.0/24 |
| 142.251.127.26 | Mail server alt2.aspmx.l.google.com | 142.251.127.0/24 |
| 192.178.213.27 | Mail server alt1.aspmx.l.google.com | 192.178.213.0/24 |
| 172.253.148.27 | Mail server alt3.aspmx.l.google.com | 172.253.148.0/24 |
| 142.250.147.27 | Mail server alt4.aspmx.l.google.com | 142.250.147.0/24 |
WHOIS of the domain justo.mx
Domain Name: justo.mx
Created On: 2018-11-14
Expiration Date: 2026-11-14
Last Updated On: 2024-11-12
Registrar: GoDaddy.com
URL: http://www.godaddy.com
Registrant:
Name: Registration Private
City: Tempe
State: Arizona
Country: United States
Administrative Contact:
Name: Registration Private
City: Tempe
State: Arizona
Country: United States
Technical Contact:
Name: Registration Private
City: Tempe
State: Arizona
Country: United States
Billing Contact:
Name: Registration Private
City: Tempe
State: Arizona
Country: United States
Name Servers:
DNS: elle.ns.cloudflare.com
DNS: hank.ns.cloudflare.com
DNSSEC DS Records:
% 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.
% The requested information ("Information") is provided only for the delegation
% of domain names and the operation of the DNS administered by NIC Mexico.
% It is absolutely prohibited to use the Information for other purposes,
% including sending not requested emails for advertising or promoting products
% and services purposes (SPAM) without the authorization of the owners of the
% Information and NIC Mexico.
% The database generated from the delegation system is protected by the
% intellectual property laws and all international treaties on the matter.
% If you need more information on the records displayed here, please contact us
% by email at [email protected] .
% If you want notify the receipt of SPAM or unauthorized access, please send a
% email to [email protected] .
% NOTA: La fecha de expiracion mostrada en esta consulta es la fecha que el
% registrar tiene contratada para el nombre de dominio en el registry. Esta
% fecha no necesariamente refleja la fecha de expiracion del nombre de dominio
% que el registrante tiene contratada con el registrar. Puede consultar la base
% de datos de Whois del registrar para ver la fecha de expiracion reportada por
% el registrar para este nombre de dominio.
% La informacion que ha solicitado se provee exclusivamente para fines
% relacionados con la delegacion de nombres de dominio y la operacion del DNS
% administrado por NIC Mexico.
% Queda absolutamente prohibido su uso para otros propositos, incluyendo el
% envio de Correos Electronicos no solicitados con fines publicitarios o de
% promocion de productos y servicios (SPAM) sin mediar la autorizacion de los
% afectados y de NIC Mexico.
% La base de datos generada a partir del sistema de delegacion, esta protegida
% por las leyes de Propiedad Intelectual y todos los tratados internacionales
% sobre la materia.
% Si necesita mayor informacion sobre los registros aqui mostrados, favor de
% comunicarse a [email protected].
% Si desea notificar sobre correo no solicitado o accesos no autorizados, favor
% de enviar su mensaje a [email protected].
% Query time: 774 msec
% WHEN: Fri Oct 02 11:44:36 UTC 2026