Skip to content
https://fortune.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
89
GRADE
B
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
6 PASS 3 REVIEW
C
IPv6 Readiness
Action
No IPv6 support
REVIEW
No IPv6 support
Info::
No IPv6 (AAAA) records found
IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.
No IPv6 Support
About 40% of internet users have IPv6. Consider adding AAAA records.

IPv6 support is increasingly important for global accessibility. About 40% of internet users have IPv6 connectivity.

Why this matters

No AAAA records — same impact as 'no IPv6 (AAAA) records'; IPv6-preferring clients pay extra latency falling back to IPv4.

Source: Google IPv6 stats

B
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
REVIEW
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.fortune.com/
200https://fortune.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://fortune.com/ → https://fortune.com/

Consistent

B
TLS Certificate Expiry & Recommendations
180 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

180
days left
0d 30d 60d 90d+

Recommended actions

  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
  • Enable OCSP stapling on your TLS server to remove a CA roundtrip and protect user privacy
A+
DNS Records
4 A records, 48 ms lookup
PASS
4 A records, 48 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 65.8.180.99, 65.8.180.19, 65.8.180.122, 65.8.180.49
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1273.awsdns-31.org, ns-1776.awsdns-30.co.uk, ns-473.awsdns-59.com, ns-585.awsdns-09.net
Info::
2 mail exchanger(s) configured
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
SPF record present in TXT
Info::
DNS resolution time: 48 ms
Got: 48 ms
A65.8.180.99, 65.8.180.19, 65.8.180.122, 65.8.180.49
AAAA—
CNAME—
NSns-1273.awsdns-31.org, ns-1776.awsdns-30.co.uk, ns-473.awsdns-59.com, ns-585.awsdns-09.net
MX
10 mx1-us1.ppe-hosted.com
20 mx2-us1.ppe-hosted.com
TXT
Ascend-verification: Ascend
Impact-Site-Verification:0c4f4006-7db7-4de7-9c44-503127ca3f9e
SFMC-JiepT-Epei0pauMWlutTEcXAkH36RHPy_akuGq6_
VC2Efb0Jw/2RSd0fAx8bSur7kItw2rx8qmebPBj6JXc85N15QNNJzVXbEWtYQOhx/URT+5cO9pftaAk2...
ZOOM_verify_ZyoZwZc9Rh68_YlIB-BdMA
ZOOM_verify_iffDNQhYTg27k7QbosbZNw
ahrefs-site-verification_39b7e330ce14a24f554844884afa983721dc1c7328bb26feafa0b65...
amazonses:IQCA6/RQqRNFamd8b0B67TH+dlb5TDEwkAE3dboWVrU=
apple-domain-verification=bKXfT4YAsXCSgpnW
asv=f9c05fe631e98c8d2627f4f00c753fc2
dailymotion-domain-verification=dm1alpcqf0ue7et04
docusign=f9ccfb90-94da-430c-959d-f77a82544b33
facebook-domain-verification=0tlg42c3k3mjni3br69f0ie5w8cpc4
fastly-domain-delegation-boccjnwotuv4zxnk7kqv-717620-2023-11-27
google-site-verification=SHoIkDSKeEM0OGZn4ygaiPM_dqcD2LVh04B0UlI_0o4
google-site-verification=SUX8rIMrer1l8vTfMlzxIedkV-gR3OBibmRa94Mm5OA
google-site-verification=WKaOZMtHsJtOGjCM1nsRqvp8I5IT5Op5xMsxPkLHpiE
google-site-verification=Z-YtF2omTVXKTWpZ9vRdF9NgvA9HAAwxcNC8QklDW4E
google-site-verification=fHwXyE_lBAiQwNJ9ADCGbTeD8VX54S3dtpgGKVh7uFI
google-site-verification=ucHyBAb2tRNq6zkSR75YRZcLM0yUr4iLRpelVPsx0ho
google-site-verification=z-iPq9kuzp7lH98teXV2uo0XJJBEHMnZdlRAGReq9zQ
jamf-site-verification=qdHOPVge2KvX9qyM4DBpzg
ppe-50ab64024af90630109a
teamviewer-sso-verification=911838b426524510bdaba4dfab7c82a7
SPF v=spf1 include:_spf.mlsend.com include:spf.protection.outlook.com include:email....
yahoo-verification-key=bhHCbUW9MiLbKejjBsO2rCZiGvHqNTHs1sdvie1iY60=
CAALookup not available with standard resolver
Resolved in 48 ms

CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.

Why this matters

Informational: CAA (Certification Authority Authorization) records weren't checked in this scan.

A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://fortune.com

https://fortune.com

20 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://fortune.com20020 msHTTP/1.1nginx
A+
Crawlability
robots.txt present, sitemap with 198 URLs
PASS
robots.txt present, sitemap with 198 URLs
Info::
robots.txt is present
Got: 1812 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 198 entries
Info::
Sitemap index with 198 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1812 B Sitemaps referenced 13 User-agents CCBot, Google-Extended, ia_archiver, omgili, omgilibot, *, Googlebot, LinkedInBot Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /search/*
Disallow: /sponsored/
Disallow: /newsletter/
Allow: */feed/*/articles.xml
Allow: /feed/sitema*
Disallow: /wp-login.php
Disallow: /wp-signup.php
Disallow: /press-this.php
Disallow: /remote-login.php
Disallow: /activate/
Disallow: /cgi-bin/
Disallow: /mshots/v1/
Disallow: /next/
Disallow: /public.api/*
Disallow: /advanced-search/*
Disallow: /genai-analytics/*
Disallow: /comscore-json/*
Disallow: /api/*
Disallow: /*.webarchive$


User-agent: Googlebot
User-agent: LinkedInBot
Disallow: /search/*
Disallow: /sponsored/
Disallow: /newsletter/
Allow: */feed/*/articles.xml
Allow: /feed/sitema*
Disallow: /wp-login.php
Disallow: /wp-signup.php
Disallow: /press-this.php
Disallow: /remote-login.php
Disallow: /activate/
Disallow: /cgi-bin/
Disallow: /mshots/v1/
Disallow: /next/
Disallow: /public.api/*
Disallow: /advanced-search/*
Disallow: /preview/*

User-agent: CCBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: ia_archiver
Disallow: /

User-Agent: omgili
Disallow: /

User-Agent: omgilibot
Disallow: /

# Google SiteMaps
Sitemap: https://fortune.com/sitemap_index.xml
Sitemap: https://fortune.com/well/sitemap_index.xml
Sitemap: https://fortune.com/crypto/sitemap_index.xml
Sitemap: https://fortune.com/asia/sitemap_index.xml
Sitemap: https://fortune.com/europe/sitemap_index.xml
Sitemap: https://fortune.com/education/sitemap_index.xml
Sitemap: https://fortune.com/company/sitemap_index.xml
Sitemap: https://fortune.com/ranking/sitemap.xml
Sitemap: https://fortune.com/author/sitemap_index.xml
Sitemap: https://fortune.com/about.xml
Sitemap: https://fortune.com/feed/googlenews/articles.xml
Sitemap: https://fortune.com/videos/sitemap.xml
Sitemap: https://fortune.com/press-releases/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 198 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
fortune.com — via MarkMonitor Inc., 32 years, 4 months old, hosted on AWS
PASS
fortune.com — via MarkMonitor Inc., 32 years, 4 months old, hosted on AWS
Info::
Domain registered until Jun 1, 2027 (1 years, 1 months remaining)
Info::
DNSSEC is not enabled
DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.
Info::
Registrar: MarkMonitor Inc.
Warning::
Registrar lock is NOT enabled
The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.
Info::
Hosting: AWS
Got: AS16509
Domain expiry

322 days

June 1, 2027

SSL certificate

180 days

Issued by Amazon

Domain age

32 years, 4 months

Registered June 2, 1994

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

65.8.180.19

Registrar

MarkMonitor Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar MarkMonitor Inc.
Created June 2, 1994 (32 years, 4 months ago)
Expires June 1, 2027 (1 years, 1 months)
Last Updated April 30, 2025
Name Servers ns-1273.awsdns-31.org, ns-1776.awsdns-30.co.uk, ns-473.awsdns-59.com, ns-585.awsdns-09.net
DNSSEC Not enabled
Hosting
IP Address 65.8.180.19
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.1s)

DNSSEC protects against DNS spoofing attacks. While not required, enabling DNSSEC adds an additional layer of security. Contact your DNS provider to enable it.

Why this matters

Without DNSSEC, an attacker who can poison your DNS can hijack your domain — and SSL certs alone don't stop them.

Learn more ▾

DNSSEC adds cryptographic signatures to DNS records, preventing forged responses from poisoning resolver caches. Without it, an attacker who controls the network path can redirect your domain to a malicious server before any HTTPS handshake happens. Most modern registrars (Cloudflare, Google Domains, Route 53) enable it with one toggle.

Source: ICANN / RFC 4033

The domain can be transferred without an unlock step. Enable registrar lock (clientTransferProhibited) in your registrar's control panel to protect against unauthorized or accidental transfers.

Why this matters

Without registrar lock, an attacker who phishes your registrar credentials can transfer the domain in minutes — total brand hijack.

Learn more ▾

Registrar lock (clientTransferProhibited, clientUpdateProhibited, clientDeleteProhibited) requires extra verification before any transfer/update/delete. Every major registrar offers it free. Combined with 2FA on your registrar account, it's the strongest defense against domain hijacking.

Source: ICANN / domain-security best practice

A+
HTTP Probe Timing
Total 23 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
5 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
3 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
19 ms
Total Time Total request time from DNS lookup through full response.
24 ms

Connection waterfall

DNS Lookup 5 ms TCP Connect 3 ms TLS Handshake 5 ms Server Processing 7 ms Content Transfer 4 ms
A+
CDN & Delivery
AWS CloudFront (Hit from cloudfront)
PASS
AWS CloudFront (Hit from cloudfront)
Info::
Site is served via AWS CloudFront CDN (edge: SFO53-P9)
Got: x-amz-cf-id: R_8WLrCKa_NjycOMwXLIUTXCi58Qax8pExeHg1OKCZgIU3vqPdAVYQ==
Info::
CDN cache status: Hit from cloudfront
CDN Detected: AWS CloudFront
Provider AWS CloudFront Cache Status Hit from cloudfront Evidence x-amz-cf-id: R_8WLrCKa_NjycOMwXLIUTXCi58Qax8pExeHg1OKCZgIU3vqPdAVYQ==
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback