Dataweaz

nytimes.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
January 18, 1994
Expires on
January 19, 2027
Name servers
dns3.p06.nsone.net, ns-635.awsdns-15.net, ns-1652.awsdns-14.co.uk, dns2.p06.nsone.net, dns1.p06.nsone.net, dns4.p06.nsone.net, ns-1328.awsdns-38.org, ns-244.awsdns-30.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

Spoofing protection (DMARC)

Reject

E-mails spoofing this domain are rejected.

DMARC tells mail servers what to do with an e-mail that claims to come from nytimes.com but fails SPF and DKIM checks.

Policy
Reject
Subdomain policy
Reject
Messages covered
100%
DKIM alignment
Relaxed
SPF alignment
Relaxed
Failure reports
—

Record

v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]

Authorized senders (SPF)

Soft

E-mails sent by any other server are accepted but flagged as suspicious.

SPF lists the servers allowed to send e-mails for nytimes.com.

RuleValueResult
includenytimes.com._nspf.vali.emailAllowed
include%{i}._ip.%{h}._ehlo.%{d}._spf.vali.emailAllowed
include_spf.e.sparkpost.comAllowed
includeamazonses.comAllowed
all—Suspicious

Top-level DNS lookups: 4 of 10 allowed

Record

v=spf1 include:nytimes.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.e.sparkpost.com include:amazonses.com ~all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
s2SendGridRSA 1024 bits · shortActive
zendesk1ZendeskRSA 2048 bitsActive
zendesk2ZendeskRSA 2048 bitsActive

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

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

nytimes.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.nytimes.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.nytimes.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.nytimes.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.nytimes.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 nytimes.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
dns3.p06.nsone.net198.51.44.70
ns-635.awsdns-15.net205.251.194.123
ns-1652.awsdns-14.co.uk205.251.198.116
dns2.p06.nsone.net198.51.45.6
dns1.p06.nsone.net198.51.44.6
dns4.p06.nsone.net198.51.45.70
ns-1328.awsdns-38.org205.251.197.48
ns-244.awsdns-30.com205.251.192.244

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @nytimes.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
1aspmx.l.google.com108.177.15.27
5alt2.aspmx.l.google.com142.251.127.27
5alt1.aspmx.l.google.com192.178.213.26
10alt3.aspmx.l.google.com172.253.148.26
10alt4.aspmx.l.google.com142.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.nytimes.com.

NameContent
nytimes.comlucidlink-verification=PZP4S4XGS2MW9TT3H76V0TPSY0
nytimes.comonetrust-domain-verification=dee1266d6a984549b43a1bd101957a8f
nytimes.comatlassian-domain-verification=Vrn33GZgJTapfeggl1snZZ5a8HjNwfFb1K5kBxVNhp7jlMFlRZGUytV9rIHhGdR8
nytimes.comadobe-idp-site-verification=5ce4d99c-af0a-4b76-9217-bd49d3336df0
nytimes.comMS=A1BFCA84E21B7011CA98DF9DC251CDDF90E0174B
nytimes.com_b2ao2yybjl1klqaw0mahepejqyvwgq1
nytimes.comnotion-domain-verification=4wS9fYEvnEgZg6Fc4cQ3atgsNuaj2zZIKwRP34uAGse
nytimes.comcursor-domain-verification-cbqk6b=DdvvVJNHMmVswd6oRmD8GZX50
nytimes.comgoogle-site-verification=tvhSn0gaSi6CUrrc9N1pvq4tmJrzvbfJbKVWPrgg_6Q
nytimes.comdocusign=bd506110-db79-430e-b159-cc1d74fe1176
nytimes.comwiz-domain-verification=f58277d3dd68296f29aace3a12b746a054eee9f6c472f21673207cfcc1991081
nytimes.comgoogle-site-verification=ZsySMeZ_SRbJZFu-53ptepytP7h5pxHO0qAg8Z2bKug
nytimes.comgoogle-site-verification=dNxU4aqYrP-m9U4J4OO_hvaOfjepywv2BN8Luc-q4o8
nytimes.comgoogle-site-verification=jZcmQFxPEP38yqYpmRvo0v_9hQFAdBZPUEBwTNUPUF8
nytimes.comMS=ms22827202
nytimes.comgoogle-site-verification=4TE2ggBoy6PktLjtZ03t32A2oEZ0VD0PY6MnTj8IL_g
nytimes.comZOOM_verify_ClSSgAI2bqqZQA66rT4Z1x
nytimes.comserval-domain-verification-bew4y4=VA1qmSGnvHaYCguEOONe1E2Nq
nytimes.comgoogle-site-verification=NSmi94k0NzvQaksUCNXeJZPYtJPSoUf52cjJsJcZFy4
nytimes.comgoogle-site-verification=aReMr8hkX3gxeHLKKk4tJ1s970U7QdEqUMIhMmLUfjQ
nytimes.comgoogle-site-verification=NIqXa_F8IaqdPJhTtexgR0NYbzVLD_-X-uRUvyf4GyQ
nytimes.comklaviyo-site-verification=NsTtn9
nytimes.comparallels-domain-verification=df31386535ac4cbe8d70cde19722e58da9831b130c3d46299f64ca5d0ed0f94d
nytimes.comklaviyo-site-verification=PkxYaQ
nytimes.comatlassian-sending-domain-verification=1b4b110f-a2dd-4853-8b13-de36c831aa81
nytimes.comsegment-site-verification=Z6wALFPYli6z0AlPlgjZXpMVRLZ2KiRb
nytimes.comgamma-domain-verification-m0hfp8=Kn1CNDywmVQvNK2EE60GxQORI
nytimes.commasv=oFbRBdtBUCoWWHaQiRJLZcKASUJZboJz
nytimes.com253961548-4297453
nytimes.comjamf-site-verification=PIprfFrz8CBhH0TK0nNhnQ
nytimes.comdocusign=6a4f88fd-cd2f-4917-acdb-bb2f343438a1
nytimes.comshade-domain-verification-wys4jv=w07FFVQR3MSW3TNoXqZAYS7O0
nytimes.comdell-technologies-domain-verification=nytimes.com_e9803e4c-210b-4501-a26b-705148cb7292_1777730473
nytimes.comv=spf1 include:nytimes.com._nspf.vali.email include:%{i}._ip.%{h}._ehlo.%{d}._spf.vali.email include:_spf.e.sparkpost.com include:amazonses.com ~all
nytimes.comapple-domain-verification=1BVLidj37w9zRMnU
nytimes.commiro-verification=ee856857f05022ca58c04ab6f8e4014e564b3d6b
nytimes.comgoogle-site-verification=q5oM_szMOT79db0AJjdk_JP1xeurksaWmhbv_dd-MEM
nytimes.comgoogle-site-verification=4qJm5sAZa1_29BTwFjqW09t7_7D4Vee3LBFQqg8xYbs
nytimes.comklaviyo-site-verification=VBhmML
nytimes.comdropbox-domain-verification=4ld3jahx0psi
nytimes.comNV=6b9b6zcshr98ey1x
nytimes.comgoogle-site-verification=ZTCMdpSKM7HwqTvGUf_00Ef008JhOnbzGgCSUGYfsro
nytimes.comgoogle-site-verification=OJl4BugQ_esE20V0QtVc9DhqvnnxOLHnf5AmFjdLSqk
nytimes.com_wufmw8f1leho148v35f8zaogcyux7lx
nytimes.comwrike-verification=NjYxMTMwODpmZGRiNmQ3Yjc1Yzk5NjFhMDk2OWI4MWM2NDhkZmYxNjdmOThhODQ2MDJmZmI0ZTMxNTUxOTMzZGRlMzQwZDEw
nytimes.comonetrust-domain-verification=1e62f8d767fc41a39fdf3f77025a8105
_dmarc.nytimes.comv=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]
google._domainkey.nytimes.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxPzd1FdX+tDLRwxu4INrM6izfw2Re6or0UJLy2FeoHMsyw3hphrHaLRFzH5EKjQc6hiBXFucXUIPMJEyw5V7hQfn/sNr93nge5bFbuvTO/N8U46OCkbm4SmK/TGpcnNnn62nvgN5bxo9UzW9D2z8josC97q0cA2G70lELRfR18EApuYCDj0ccfmCLyOwItCeav1yMHAIbg9z50mrTTL2lHh6J4iQcOIj5cdz8VQwnUnBCOOuGUteOd1JNR0yEx8UchBqcntQe4ktag7I4xCwxrXhmleCJeT0+9DDpuROICna0CqO2QMWqjdp8qeYdM/RW3rQx3uhprSTIUWeMM2LWwIDAQAB
k2._domainkey.nytimes.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.nytimes.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
s2._domainkey.nytimes.comk=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDgq4WY8wH4aXqOltolkyjnUGMTJ1T6k9YscUFOesyEs68aiMRz0Kg594jiqfi6p2MVD8bbVyPEEGypzvdCcF2dX1Yv2v082ntk9UYi1Hf9GAL83R7tfirm1XHc9c1hsAq0twzfOzDPZ/bLIgfMxHHPY5+Lbt0HJHhmMSr7T8EyEQIDAQAB
zendesk1._domainkey.nytimes.comv=DKIM1;t=s;n=core;k=rsa;p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA9IqdLrO3Zr2/56MHt8oQVCQorP0Bl2Fz9sM2tFBnJCdB/HogQmuudEg2xAovCN2PYpw44UijIvPuBoT9vxiv6ZCBJTLJXa82r6ke5rE4tbe9NKFIrVIb9S306cJDrnKFMDb8p0dU/Su0+eUR5gVAOtCuz2L8HAzs5edvsEvD/Fb4ny1RLNSEPZkIQLfGhVxQeWANm3+1Jwb/OBVXV9k0nKpWrpgqcmO7NzroJirp014RQY7rGi60JLUubc6XhvoFQBQrtOAdVlZC5wvfS1bgpq5kQpdP7cajIqWCeqxPTeo0ZUpey2ZcaygEsZz0Z3Gs5wDzyuqd7/ADpr2jNF7ozwIDAQAB
zendesk2._domainkey.nytimes.comv=DKIM1; t=s; n=core; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAmiSFNkgXrO3I8aOaPONDZWHv027rkiGIwb838OyXPgvFDEkCV/qGcdXSjZnaVAadrTm/oKnL8WOltP9zB1FLEuKt0fTi5zRyKPE4oIYCnEzXwrGqzjUcCABQBawQVqvXjDOaYh9Lhp8W5PYOLo905vRW7ipyIMDhuzBOJls91/WWXnNK0OwP3RghiisZjA3K2KqtRwf7w6GjNeNuAMNhvcmgAN15d/mhK+dev/hcRbal66RoYyTD8c0F0isahWH0envEX8aj+SBhheNk0/U37dGE+4nFaY5yP9CUlYjFKDSIKZgHzG4Hci3t/RubU58pi6BCrQQdAFvIOeDFeCZ0ywIDAQAB

Related IP addresses

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

IP addressUsed for/24 block
151.101.65.164Website151.101.65.0/24
151.101.129.164Website151.101.129.0/24
151.101.193.164Website151.101.193.0/24
151.101.1.164Website151.101.1.0/24
198.51.44.70Name server dns3.p06.nsone.net198.51.44.0/24
205.251.194.123Name server ns-635.awsdns-15.net205.251.194.0/24
205.251.198.116Name server ns-1652.awsdns-14.co.uk205.251.198.0/24
198.51.45.6Name server dns2.p06.nsone.net198.51.45.0/24
198.51.44.6Name server dns1.p06.nsone.net198.51.44.0/24
198.51.45.70Name server dns4.p06.nsone.net198.51.45.0/24
205.251.197.48Name server ns-1328.awsdns-38.org205.251.197.0/24
205.251.192.244Name server ns-244.awsdns-30.com205.251.192.0/24
108.177.15.27Mail server aspmx.l.google.com108.177.15.0/24
142.251.127.27Mail server alt2.aspmx.l.google.com142.251.127.0/24
192.178.213.26Mail server alt1.aspmx.l.google.com192.178.213.0/24
172.253.148.26Mail server alt3.aspmx.l.google.com172.253.148.0/24
142.250.147.27Mail server alt4.aspmx.l.google.com142.250.147.0/24

WHOIS of the domain nytimes.com

Domain Name: NYTIMES.COM
   Registry Domain ID: 91991_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2024-12-18T11:11:19Z
   Creation Date: 1994-01-18T05:00:00Z
   Registry Expiry Date: 2027-01-19T05:00:00Z
   Registrar: MarkMonitor Inc.
   Registrar IANA ID: 292
   Registrar Abuse Contact Email: [email protected]
   Registrar Abuse Contact Phone: +1.2086851750
   Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
   Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
   Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
   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: DNS1.P06.NSONE.NET
   Name Server: DNS2.P06.NSONE.NET
   Name Server: DNS3.P06.NSONE.NET
   Name Server: DNS4.P06.NSONE.NET
   Name Server: NS-1328.AWSDNS-38.ORG
   Name Server: NS-1652.AWSDNS-14.CO.UK
   Name Server: NS-244.AWSDNS-30.COM
   Name Server: NS-635.AWSDNS-15.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T15:56:28Z <<<

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.