Dataweaz

prodigy.net.mx

Summary

Registrar
Telmex
Status
Distrito
Created on
February 16, 1999
Expires on
February 15, 2027
Name servers
nsmty1.uninet.net.mx, nsgdl1.uninet.net.mx, nsmex1.uninet.net.mx, dnsadm-interno.uninet.net.mx
Mail servers
publicms2.mail2world.com, publicms3.mail2world.com, publicms1.mail2world.com
DKIM
No key found among the common selectors

Spoofing protection (DMARC)

Monitoring

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 prodigy.net.mx but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=none; aspf=s; adkim=r; 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 prodigy.net.mx.

RuleValueResult
ip4200.57.160.146/29Allowed
ip4209.67.128.0/23Allowed
ip474.202.142.0/24Allowed
ip4216.163.188.0/24Allowed
ip4148.235.52.0/26Allowed
ip4187.191.73.0/24Allowed
ip4200.57.141.0/24Allowed
ip469.49.113.0/24Allowed
ip474.116.88.0/22Allowed
ip4216.55.172.0/24Allowed
mx—Allowed
includerelay.mailchannels.netAllowed
all—Rejected

Top-level DNS lookups: 2 of 10 allowed

Record

v=spf1 ip4:200.57.160.146/29 ip4:209.67.128.0/23 ip4:74.202.142.0/24 ip4:216.163.188.0/24 ip4:148.235.52.0/26 ip4:187.191.73.0/24 ip4:200.57.141.0/24 ip4:69.49.113.0/24 ip4:74.116.88.0/22 ip4:216.55.172.0/24 mx include:relay.mailchannels.net -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 prodigy.net.mx arrive; SPF, DKIM and DMARC let mail servers check that an e-mail claiming to come from prodigy.net.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 @prodigy.net.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

prodigy.net.mx  MX  10 mx1.prodigy.net.mx.
prodigy.net.mx  MX  20 mx2.prodigy.net.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.prodigy.net.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

prodigy.net.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.prodigy.net.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.prodigy.net.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.prodigy.net.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.prodigy.net.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 prodigy.net.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.

TypeIP address
A148.235.52.179

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
nsmty1.uninet.net.mx—
nsgdl1.uninet.net.mx200.23.242.197
nsmex1.uninet.net.mx200.33.146.197
dnsadm-interno.uninet.net.mx200.33.150.193

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @prodigy.net.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.

PriorityServerIP address
10publicms2.mail2world.com35.167.34.51
10publicms3.mail2world.com54.88.152.217
10publicms1.mail2world.com44.237.12.42

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.prodigy.net.mx.

NameContent
prodigy.net.mxv=spf1 ip4:200.57.160.146/29 ip4:209.67.128.0/23 ip4:74.202.142.0/24 ip4:216.163.188.0/24 ip4:148.235.52.0/26 ip4:187.191.73.0/24 ip4:200.57.141.0/24 ip4:69.49.113.0/24 ip4:74.116.88.0/22 ip4:216.55.172.0/24 mx include:relay.mailchannels.net -all
prodigy.net.mxpcd5jnjvb8wkpn25f15282s8xcqvqkzh
_dmarc.prodigy.net.mxv=DMARC1; p=none; aspf=s; adkim=r; rua=mailto:[email protected]

Related IP addresses

IPv4 addresses used by prodigy.net.mx: website, name servers, mail servers and senders authorized by SPF.

IP addressUsed for/24 block
148.235.52.179Website148.235.52.0/24
200.23.242.197Name server nsgdl1.uninet.net.mx200.23.242.0/24
200.33.146.197Name server nsmex1.uninet.net.mx200.33.146.0/24
200.33.150.193Name server dnsadm-interno.uninet.net.mx200.33.150.0/24
35.167.34.51Mail server publicms2.mail2world.com35.167.34.0/24
54.88.152.217Mail server publicms3.mail2world.com54.88.152.0/24
44.237.12.42Mail server publicms1.mail2world.com44.237.12.0/24

WHOIS of the domain prodigy.net.mx

Domain Name:       prodigy.net.mx

Created On:        1999-02-16
Expiration Date:   2027-02-15
Last Updated On:   2026-02-19
Registrar:         Telmex
URL:               http://www.telmex.com

Registrant:
   Name:           Ricardo Hajj Kuri
   City:           Mexico
   State:          Distrito Federal
   Country:        Mexico

Administrative Contact:
   Name:           Mario A. Salgado Carvajal
   City:           MEXICO
   State:          Ciudad de Mexico
   Country:        Mexico

Technical Contact:
   Name:           FRANCISCO MARTINEZ FLORES
   City:           DF
   State:          Ciudad de Mexico
   Country:        Mexico

Billing Contact:
   Name:           MARIA DE LA LUZ REYES RODRIGUEZ
   City:           DF
   State:          Ciudad de Mexico
   Country:        Mexico

Name Servers:
   DNS:            nsgdl1.uninet.net.mx       200.23.242.197
   DNS:            nsmty1.uninet.net.mx       200.33.148.197
   DNS:            nsmex1.uninet.net.mx       200.33.146.197

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: 742 msec
% WHEN: Fri Oct 02 10:26:57 UTC 2026