Dataweaz

fortune.com

Summary

Registrar
MarkMonitor Inc.
Status
clientDeleteProhibited
Created on
June 2, 1994
Expires on
June 1, 2027
Name servers
ns-585.awsdns-09.net, ns-1273.awsdns-31.org, ns-473.awsdns-59.com, ns-1776.awsdns-30.co.uk
Mail servers
mx1-us1.ppe-hosted.com, mx2-us1.ppe-hosted.com
DMARC
Reject

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 fortune.com but fails SPF and DKIM checks.

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

Record

v=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected],mailto:[email protected], mailto:[email protected]; fo=1; pct=100; rf=afrf

Authorized senders (SPF)

Strict

E-mails sent by any other server are rejected.

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

RuleValueResult
include_spf.mlsend.comAllowed
includespf.protection.outlook.comAllowed
includeemail.prnewswire.comAllowed
include_spf.salesforce.comAllowed
includeu826348.wl.sendgrid.netAllowed
includespf.braintreegateway.comAllowed
adispatch-us.ppe-hosted.comAllowed
mx—Allowed
ip454.236.128.150Allowed
ip454.236.109.30Allowed
ip454.236.128.150Allowed
ip454.236.109.30Allowed
ip440.76.81.49Allowed
ip4204.14.234.64/28Allowed
ip4204.14.232.64/28Allowed
ip4182.50.78.64/28Allowed
ip496.43.144.64/31Allowed
ip496.43.148.64/31Allowed
all—Rejected

Top-level DNS lookups: 8 of 10 allowed

Record

v=spf1 include:_spf.mlsend.com include:spf.protection.outlook.com include:email.prnewswire.com include:_spf.salesforce.com   include:u826348.wl.sendgrid.net include:spf.braintreegateway.com a:dispatch-us.ppe-hosted.com mx ip4:54.236.128.150 ip4:54.236.109.30 ip4:54.236.128.150 ip4:54.236.109.30 ip4:40.76.81.49 ip4:204.14.234.64/28 ip4:204.14.232.64/28 ip4:182.50.78.64/28 ip4:96.43.144.64/31 ip4:96.43.148.64/31 -all

E-mail signing (DKIM)

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

SelectorLikely serviceKeyStatus
googleGoogle WorkspaceRSA 2048 bitsActive
selector1Microsoft 365RSA 1024 bits · shortActive
k2MailchimpRSA 2048 bitsActive
k3MailchimpRSA 2048 bitsActive
mandrillMandrillRSA 1024 bits · shortActive

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

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

fortune.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.fortune.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.fortune.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.fortune.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.fortune.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 fortune.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
ns-585.awsdns-09.net205.251.194.73
ns-1273.awsdns-31.org205.251.196.249
ns-473.awsdns-59.com205.251.193.217
ns-1776.awsdns-30.co.uk205.251.198.240

Mail servers (MX)

MX records point to the servers that receive e-mails sent to the domain, that is to @fortune.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
10mx1-us1.ppe-hosted.com67.231.154.162
20mx2-us1.ppe-hosted.com67.231.154.163

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.fortune.com.

NameContent
fortune.comv=spf1 include:_spf.mlsend.com include:spf.protection.outlook.com include:email.prnewswire.com include:_spf.salesforce.com include:u826348.wl.sendgrid.net include:spf.braintreegateway.com a:dispatch-us.ppe-hosted.com mx ip4:54.236.128.150 ip4:54.236.109.30 ip4:54.236.128.150 ip4:54.236.109.30 ip4:40.76.81.49 ip4:204.14.234.64/28 ip4:204.14.232.64/28 ip4:182.50.78.64/28 ip4:96.43.144.64/31 ip4:96.43.148.64/31 -all
fortune.comgoogle-site-verification=ucHyBAb2tRNq6zkSR75YRZcLM0yUr4iLRpelVPsx0ho
fortune.comfastly-domain-delegation-boccjnwotuv4zxnk7kqv-717620-2023-11-27
fortune.comyahoo-verification-key=bhHCbUW9MiLbKejjBsO2rCZiGvHqNTHs1sdvie1iY60=
fortune.comImpact-Site-Verification:0c4f4006-7db7-4de7-9c44-503127ca3f9e
fortune.comjamf-site-verification=qdHOPVge2KvX9qyM4DBpzg
fortune.comamazonses:IQCA6/RQqRNFamd8b0B67TH+dlb5TDEwkAE3dboWVrU=
fortune.comgoogle-site-verification=3I_zCpHizO9KLtfvRAApte9CqfaoB6VWdVH0eTvL5vU
fortune.comgoogle-site-verification=SHoIkDSKeEM0OGZn4ygaiPM_dqcD2LVh04B0UlI_0o4
fortune.comgoogle-site-verification=SUX8rIMrer1l8vTfMlzxIedkV-gR3OBibmRa94Mm5OA
fortune.comgoogle-site-verification=f_V4t4DUaxlKA019zi3sVF2W0RUHOcGlVu_6Ke-li8E
fortune.comgoogle-site-verification=sl0jr1GuIT3iPNaGxMEU-WYqCP0BvX5Wtacc1R1zrp0
fortune.comgoogle-site-verification=fHwXyE_lBAiQwNJ9ADCGbTeD8VX54S3dtpgGKVh7uFI
fortune.comanthropic-domain-verification-wtgkzt=Q53U2xvHxiIBCvStySB0WPACK
fortune.comSFMC-JiepT-Epei0pauMWlutTEcXAkH36RHPy_akuGq6_
fortune.comdocusign=f9ccfb90-94da-430c-959d-f77a82544b33
fortune.comppe-50ab64024af90630109a
fortune.comZOOM_verify_ZyoZwZc9Rh68_YlIB-BdMA
fortune.comlemlist-verif=-3438f014
fortune.comahrefs-site-verification_39b7e330ce14a24f554844884afa983721dc1c7328bb26feafa0b65ba2963ce9
fortune.comlemlist-verif=-2006af5b
fortune.comAscend-verification: Ascend
fortune.comapple-domain-verification=bKXfT4YAsXCSgpnW
fortune.comgoogle-site-verification=z-iPq9kuzp7lH98teXV2uo0XJJBEHMnZdlRAGReq9zQ
fortune.comteamviewer-sso-verification=911838b426524510bdaba4dfab7c82a7
fortune.comfacebook-domain-verification=0tlg42c3k3mjni3br69f0ie5w8cpc4
fortune.comasv=f9c05fe631e98c8d2627f4f00c753fc2
fortune.comdailymotion-domain-verification=dm1alpcqf0ue7et04
fortune.comVC2Efb0Jw/2RSd0fAx8bSur7kItw2rx8qmebPBj6JXc85N15QNNJzVXbEWtYQOhx/URT+5cO9pftaAk2uJjQ5g==
fortune.comgoogle-site-verification=WKaOZMtHsJtOGjCM1nsRqvp8I5IT5Op5xMsxPkLHpiE
fortune.comgoogle-site-verification=Z-YtF2omTVXKTWpZ9vRdF9NgvA9HAAwxcNC8QklDW4E
fortune.comZOOM_verify_iffDNQhYTg27k7QbosbZNw
_dmarc.fortune.comv=DMARC1; p=reject; rua=mailto:[email protected],mailto:[email protected]; ruf=mailto:[email protected],mailto:[email protected], mailto:[email protected]; fo=1; pct=100; rf=afrf
google._domainkey.fortune.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr8AjushC8HSKIOrTszenqcniX3LHQyzpZoxsrVufVB88HVXOJY5hk0OZpNsGGro3Xq7JDqz7B1YEnCCj0baAPbSAl4BVNRO8eHdf3gcBFQOGt8YfEQPHwQtG3+z7FU9ZFM6rMmd1lYN/UY7BDv8Pd2dQOUD7QCSMc3qF6NcROomqO2fC/i0pFo2rLseypqGbgoBkDsXQHiyefFGW+jYGjcEVsoVQRSim1FF9oiuZ8pCBNm7KXow/lZmVkZ2i+uF0ZuIxu0HT7wZdsFltHw03BIqvp9HeuHA13SBuGJqDgJWbTLaXRRkLXJuLA9xJFOem8BzSs8m9HKuuatuzX8dFsQIDAQAB
selector1._domainkey.fortune.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDLWPTJjiR4k1DM/aUM9UG6CeV/vBFv+F8Us2qdIwmZDnrnkE1Q/2FBT9Ls0iCwJRADRFGEjDBd80+4IyKnX6RtzkcrE+OOIis584ozpbhpR3OQtnmSjuPi3Ld1aNH8YQJlB7sTmnda0Ha6/8qBs1Q+k0ooNIUXXH2Jz0xonBpD2QIDAQAB;
k2._domainkey.fortune.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAv2aC2KjGKLOwTweBY5A9RpjsxaBXR9r7OAU6U8/zn92ivImI75naUujWbItRI/QmL1jy5PWGqLwoUA0b90ObWaLDc+i9MtTNmGeWO009hr20fIxhGg6XBT2kjZ1DTThopSe1nAndsupmcBwlQ5Q6LJ+ZAxLcujnPIxM0ZBLmgpkv8u6RfY4eFP8OLvdAW3oSuB0DyLDigQX4Sj8wBO4YIdQH6AAmBeOsidsKAFNFUCpc3vCxtBDR12U+cBg724l3sBkMQ8evnz6idnqxq9QAVYh8k4kJ+RP+6cqTdy7LjIm8xY/bQNpQIpGUAuDo2DjLcCDun9DAI4Q/3z+Q0o9QuQIDAQAB;
k3._domainkey.fortune.comv=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsYGiMSn7fsUqSvfSX40x9R1OlRtbNiCY80lHRIlcKx3XDIR7257aUx+q9CSIARdfTL6KCuLGNFx5g9TgVr6png4ajcieSQGtOehBgxnkDN8aAA5TX0FmFrcefJU0JoxLOF09EKgXxhSSHCk/ekVb0PXSboHXoZ9+EI404F1qhcwXXIgHXTaUthHTut2P6BBZhIXIgvDe/w49GchR7MRJqjNb7neEBbYHbgWuBTvvHCg7Gy6m6n9krYK+ROWq3dVvXy9plAGK3ygM+HtjIiMt7arRGMOF0WgDTz7YdN9BGpt6BvXxLnjiQcgS5T9n+cIyPZgiWzDMXNlaEEdKTEKxrwIDAQAB;
mandrill._domainkey.fortune.comv=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCrLHiExVd55zd/IQ/J/mRwSRMAocV/hMB3jXwaHH36d9NaVynQFYV8NaWi69c1veUtRzGt7yAioXqLj7Z4TeEUoOLgrKsn8YnckGs9i3B3tVFB+Ch/4mPhXWiNfNdynHWBcPcbJ8kjEQ2U8y78dHZj1YeRXXVvWob2OaKynO8/lQIDAQAB;

Related IP addresses

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

IP addressUsed for/24 block
99.86.109.120Website99.86.109.0/24
99.86.109.17Website99.86.109.0/24
99.86.109.115Website99.86.109.0/24
99.86.109.106Website99.86.109.0/24
205.251.194.73Name server ns-585.awsdns-09.net205.251.194.0/24
205.251.196.249Name server ns-1273.awsdns-31.org205.251.196.0/24
205.251.193.217Name server ns-473.awsdns-59.com205.251.193.0/24
205.251.198.240Name server ns-1776.awsdns-30.co.uk205.251.198.0/24
67.231.154.162Mail server mx1-us1.ppe-hosted.com67.231.154.0/24
67.231.154.163Mail server mx2-us1.ppe-hosted.com67.231.154.0/24
54.236.128.150Authorized by SPF54.236.128.0/24
54.236.109.30Authorized by SPF54.236.109.0/24
40.76.81.49Authorized by SPF40.76.81.0/24

WHOIS of the domain fortune.com

Domain Name: FORTUNE.COM
   Registry Domain ID: 105970_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.markmonitor.com
   Registrar URL: http://www.markmonitor.com
   Updated Date: 2025-04-30T10:26:47Z
   Creation Date: 1994-06-02T04:00:00Z
   Registry Expiry Date: 2027-06-01T04: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
   Name Server: NS-1273.AWSDNS-31.ORG
   Name Server: NS-1776.AWSDNS-30.CO.UK
   Name Server: NS-473.AWSDNS-59.COM
   Name Server: NS-585.AWSDNS-09.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2026-10-01T21:36:58Z <<<

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.