Skip to content
https://cosmopolitan.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
84
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
9
5 PASS 3 REVIEW 1 FIX
D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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.cosmopolitan.com/
200https://cosmopolitan.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Add the preload directive and submit to hstspreload.org once max-age + includeSubDomains are in place
  • 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, 1035 ms lookup
PASS
4 A records, 1035 ms lookup
Info::
Resolves to 4 IPv4 address(es)
Got: 151.101.0.155, 151.101.128.155, 151.101.192.155, 151.101.64.155
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1605.awsdns-08.co.uk, ns-1240.awsdns-27.org, ns-883.awsdns-46.net, ns-460.awsdns-57.com
Info::
1 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
Warning::
DNS resolution is slow (1035 ms)
Slow DNS adds latency to every page load. Consider a faster DNS provider.
Got: 1035 ms
A151.101.0.155, 151.101.128.155, 151.101.192.155, 151.101.64.155
AAAA—
CNAME—
NSns-1605.awsdns-08.co.uk, ns-1240.awsdns-27.org, ns-883.awsdns-46.net, ns-460.awsdns-57.com
MX
10 cosmopolitan-com.mail.protection.outlook.com
TXT
google-site-verification:n3g_KffTJ7RbzVSSNjRRgQaoCRczCmueK21fbjqG2hs
facebook-domain-verification=fx1nbdfy2y302jn480g0m6mt6qw4wh
MS=ms25592323
google-site-verification=9QqScyr6oRc1iBU6yEjb9Ww8aQvv8v-cCm0TKu2J2iw
tollbit-domain-verification=8b3ef2b5ab07a439195baa73521796d4de6844bbd3c8b292099e...
BSI91896679786
_globalsign-domain-verification=2wRqY6IrIINLY7B8Qcp-qur9HsiRTO04g4gwsMmFy3
google-site-verification=b3WyY6fVUjawR9Gi3rQA8uqKpdxEg7tAjbZFtJ7X8TQ
SPF v=spf1 include:aspmx.sailthru.com include:spf.protection.outlook.com ip4:205.220...
e989736710b4404cbb8f0c59a2b64716
yahoo-verification-key=nlsMqTrcLV9eJCdDEkHrkni7kdluniVieU+xUEXAJNI=
fastly-domain-delegation-tHoPyhjKot-363395-2021-04-28
lAKOtIo4abNJ307I7tjqI2z6sdOZYtNOPUPWysa+XmvPhqjL36ppgdmVpxuDbLZkWaiy0hdqkre09sp7...
fastly-domain-delegation-vpdz343jtumbqmhwtp4k-747721-2024-03-13
CAALookup not available with standard resolver
Resolved in 1035 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.

Slow DNS adds latency to every page load. Consider a faster DNS provider.

Why this matters

DNS resolution is slow — anycast DNS providers (Cloudflare, Route 53) typically resolve <50ms globally.

Source: DNS performance benchmarks

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

https://cosmopolitan.com

4 ms · HTTP/1.1

301

https://www.cosmopolitan.com/

55 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://cosmopolitan.com3014 msHTTP/1.1
2https://www.cosmopolitan.com/20055 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 9 URLs
PASS
robots.txt present, sitemap with 9 URLs
Info::
robots.txt is present
Got: 1131 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 9 entries
Info::
Sitemap index with 9 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1131 B Sitemaps referenced 4 User-agents AmazonAdBot, Google-InspectionTool, ChatGPT-User, GPTBot, OAI-SearchBot, * Blocking No — crawling allowed

User-agent: AmazonAdBot
User-agent: Google-InspectionTool
Disallow:

User-agent: ChatGPT-User
User-agent: GPTBot
User-agent: OAI-SearchBot
Disallow: /au/
Disallow: /cn/
Disallow: /dk/
Disallow: /en/
Disallow: /es/
Disallow: /in/
Disallow: /it/
Disallow: /jp/
Disallow: /ng/
Disallow: /nl/
Disallow: /no/
Disallow: /se/
Disallow: /ua/
Disallow: /uk/

User-agent: ChatGPT-User
User-agent: GPTBot
User-agent: OAI-SearchBot
User-agent: *
Disallow: /auth/
Disallow: /preview/
Disallow: /au/preview/
Disallow: /cn/preview/
Disallow: /dk/preview/
Disallow: /en/preview/
Disallow: /es/preview/
Disallow: /in/preview/
Disallow: /it/preview/
Disallow: /jp/preview/
Disallow: /ng/preview/
Disallow: /nl/preview/
Disallow: /no/preview/
Disallow: /se/preview/
Disallow: /tw/preview/
Disallow: /ua/preview/
Disallow: /uk/preview/
Disallow: /search
Disallow: /*moapt-data.js
Disallow: /_p/afflink/



Sitemap: https://www.cosmopolitan.com/sitemap_index.xml
Sitemap: https://www.cosmopolitan.com/sitemap_google_news.xml


Sitemap: https://www.cosmopolitan.com/uk/sitemap_index.xml
Sitemap: https://www.cosmopolitan.com/uk/sitemap_google_news.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 9 entries Valid XML Yes
Child Sitemaps:
A
Domain Intelligence
cosmopolitan.com — via CSC Corporate Domains, Inc., 29 years, 2 months old, hosted on Fastly
PASS
cosmopolitan.com — via CSC Corporate Domains, Inc., 29 years, 2 months old, hosted on Fastly
Warning::
Domain expires in 89 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Jul 20, 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: CSC Corporate Domains, 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: Fastly
Got: AS54113
Domain expiry

4 days

July 20, 2026

SSL certificate

173 days

Issued by GlobalSign nv-sa

Domain age

29 years, 2 months

Registered July 21, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Fastly

ASN AS54113

151.101.128.155

Registrar

CSC Corporate Domains, Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar CSC Corporate Domains, Inc.
Created July 21, 1997 (29 years, 2 months ago)
Expires July 20, 2026 (2 months)
Last Updated July 16, 2025
Name Servers ns-1240.awsdns-27.org, ns-1605.awsdns-08.co.uk, ns-460.awsdns-57.com, ns-883.awsdns-46.net
DNSSEC Not enabled
Hosting
IP Address 151.101.128.155
ASN AS54113 (FASTLY - Fastly, Inc., US)
Provider Fastly
Data source: rdap (0.3s)

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

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 34 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
28 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
0 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.
34 ms
Total Time Total request time from DNS lookup through full response.
34 ms

Connection waterfall

DNS Lookup 28 ms TCP Connect 0 ms TLS Handshake 5 ms Server Processing 1 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