Skip to content
https://www.medium.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
95
GRADE
A
FIX
0
REVIEW
2
PASS
7
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
7 PASS 2 REVIEW
B
TLS Certificate Expiry & Recommendations
67 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: 9e719205fbb7c4fb-EWR
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9e719205fbb7c4fb-EWR
A
DNS Records
2 A records, 21 ms lookup
PASS
2 A records, 21 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 162.159.153.4, 162.159.152.4
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:7::a29f:9904, 2606:4700:7::a29f:9804
Info::
No NS records found
Info::
No MX records — email not configured via DNS
Info::
CAA records not checked
CAA record lookup requires a specialized DNS resolver. This check will be available in a future update.
Info::
No SPF record found in TXT records
SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.
Info::
DNS resolution time: 21 ms
Got: 21 ms
A162.159.153.4, 162.159.152.4
AAAA2606:4700:7::a29f:9904, 2606:4700:7::a29f:9804
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 21 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.

SPF helps prevent email spoofing. Add a TXT record starting with 'v=spf1'.

Why this matters

Without SPF, receiving servers can't validate sending IPs — your domain is easier to spoof in phishing.

Learn more ▾

SPF complements DMARC. Both should be published. SPF records list authorized sending IPs (e.g., `v=spf1 include:_spf.google.com ~all` for Google Workspace). After publishing, verify in Google Postmaster Tools or mxtoolbox.

Source: RFC 7208 (SPF)

A
Redirect Chain
1 redirect(s), 77 ms total
PASS
1 redirect(s), 77 ms total
Info::
Single redirect
Got: https://www.medium.com → https://medium.com/ (301)
Info::
WWW normalization redirect

https://www.medium.com

19 ms · HTTP/1.1

301

https://medium.com/

57 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.medium.com30119 msHTTP/1.1cloudflare
2https://medium.com/20057 msHTTP/1.1cloudflare

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (2 ms)
PASS
IPv6 reachable (2 ms)
Info::
IPv6 is configured and reachable at 2606:4700:7::a29f:9904, 2606:4700:7::a29f:9804
Got: 2 ms connect
IPv6 Ready
AAAA Records 2606:4700:7::a29f:9904, 2606:4700:7::a29f:9804 Connection Reachable (2 ms)
A+
Crawlability
robots.txt present, sitemap with 27080 URLs
PASS
robots.txt present, sitemap with 27080 URLs
Info::
robots.txt is present
Got: 884 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 27080 entries
Info::
Sitemap index with 27080 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 884 B Sitemaps referenced 1 User-agents Applebot-Extended, Bytespider, FacebookBot, GPTBot, Amazonbot, ClaudeBot, GoogleOther, meta-externalagent, * Blocking No — crawling allowed
User-Agent: *
Disallow: /m/
Disallow: /me/
Disallow: /@me$
Disallow: /@me/
Disallow: /*/edit$
Disallow: /*/*/edit$
Disallow: /media/
Disallow: /p/*/share
Disallow: /r/
Disallow: /trending
Disallow: /search?q$
Disallow: /search?q=
Disallow: /*/search?q=
Disallow: /*/search/*?q=
Disallow: /*/*source=
Allow: /_/api/users/*/meta
Allow: /_/api/users/*/profile/stream
Allow: /_/api/posts/*/responses
Allow: /_/api/posts/*/responsesStream
Allow: /_/api/posts/*/related
User-Agent: Amazonbot
User-Agent: Applebot-Extended
User-Agent: Bytespider
User-Agent: ClaudeBot
User-Agent: FacebookBot
User-Agent: GoogleOther
User-Agent: GPTBot
User-Agent: meta-externalagent
Disallow: /
Allow: /about
Allow: /business
Allow: /earn
Allow: /gift
Allow: /membership
Allow: /partner-program
Allow: /verified-authors
Sitemap: https://medium.com/sitemap/sitemap.xml
License: https://medium.com/license.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 27080 entries Valid XML Yes
Child Sitemaps:
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

200https://www.medium.com/
403https://medium.com/

HTTP → HTTPS

301http://www.medium.com/ → https://medium.com/

Consistent

A
Domain Intelligence
medium.com — via Amazon Registrar, Inc., 28 years, 3 months old
PASS
medium.com — via Amazon Registrar, Inc., 28 years, 3 months old
Warning::
Domain expires in 51 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires May 26, 2026
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: Amazon Registrar, Inc.
Domain expiry

EXPIRED

May 26, 2026

SSL certificate

67 days

Issued by Google Trust Services

Domain age

28 years, 3 months

Registered May 27, 1998

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:7::a29f:9904

Registrar

Amazon Registrar, Inc.

Lock status unknown 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Domain has EXPIRED — renew immediately to avoid total site outage
  • Enable DNSSEC to protect visitors from DNS spoofing
Registrar Amazon Registrar, Inc.
Created May 27, 1998 (28 years, 3 months ago)
Expires May 26, 2026 (1 months)
Last Updated April 21, 2025
Name Servers alina.ns.cloudflare.com, kip.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:7::a29f:9904
Data source: rdap (0.0s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

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

Connection waterfall

DNS Lookup 4 ms TCP Connect 2 ms TLS Handshake 7 ms Server Processing 15 ms Content Transfer 0 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback