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

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
85
GRADE
B
FIX
1
REVIEW
3
PASS
5
INFO
0
Probed from New York, United Stated
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.variety.com/
200https://variety.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

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

Recommended actions

  • Extend HSTS max-age to at least 31536000 (1 year) to meet the preload list criteria
  • Add includeSubDomains to the HSTS directive
  • 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
1 A records, 80 ms lookup
PASS
1 A records, 80 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.176
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: variety.com
Info::
4 nameserver(s) configured
Got: ns-1716.awsdns-22.co.uk, ns-534.awsdns-02.net, ns-74.awsdns-09.com, ns-1155.awsdns-16.org
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
Info::
DNS resolution time: 80 ms
Got: 80 ms
A192.0.66.176
AAAA—
CNAMEvariety.com
NSns-1716.awsdns-22.co.uk, ns-534.awsdns-02.net, ns-74.awsdns-09.com, ns-1155.awsdns-16.org
MX
0 variety-com.mail.protection.outlook.com
TXT
google-site-verification=a57WkaJ7gY88KSKPY3GLxJKjPcFEP-nGLyoLCM8YCaY
pardot1033643=813c7da71994399f15e791e9326f22e0ad809f2957b8758fa0fb8bb3cf9fa65e
MS=ms74280155
adobe-idp-site-verification=5f299ac5ccddedab8418f37aad62a1ff499e5979c3b247bd4229...
SFMC-FtOnNSRniTlAws8RMRceqyR9oQdxxan3VnuFzB2P
SPF v=spf1 include:spf.protection.outlook.com include:_spf.salesforce.com include:as...
tollbit-domain-verification=d9921f051e47267cb4074cd391b300744adadba3f2ad8ed39652...
atlassian-domain-verification=nprFKP7f9bTtDxCbcLk3c0Ag6DYYRzhq/pIp/XJkAvuuP9aQ2b...
google-site-verification=pIaVGAxDGm9Q_ep5BU7dC3FF_zbbdPVZlKMEYZp3UeE
facebook-domain-verification=97nqs8w0mjgb6y2nm64wq1ul057n4u
spf2.0/pra include:spf.protection.outlook.com include:aspmx.pardot.com ~all
CAALookup not available with standard resolver
Resolved in 80 ms

Multiple A records provide failover if one server goes down.

Why this matters

Single A record means a single point of failure — if that IP goes down, your site is unreachable until DNS TTL expires.

Learn more ▾

Add multiple A records for round-robin failover, or use a managed DNS provider with health-checked failover (Route 53, Cloudflare, NS1). Short TTL (60-300s) lets clients recover faster on outages.

Source: SRE practice / DNS architecture

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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
1 redirect(s), 496 ms total
PASS
1 redirect(s), 496 ms total
Info::
Single redirect
Got: https://www.variety.com → https://variety.com/ (301)
Info::
WWW normalization redirect

https://www.variety.com

69 ms · HTTP/1.1

301

https://variety.com/

427 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.variety.com30169 msHTTP/1.1nginx
2https://variety.com/200427 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1380 URLs
PASS
robots.txt present, sitemap with 1380 URLs
Info::
robots.txt is present
Got: 1283 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1380 entries
Info::
Sitemap index with 1380 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 1283 B Sitemaps referenced 2 User-agents ClaudeBot, Google-Extended, Meta-ExternalFetcher, YouBot, cXensebot, anthropic-ai, Applebot-Extended, DeepSeek, Diffbot, Webzio-Extended, *, Bytespider, CCBot, ChatGPT-User, DeepSeekBot, PerplexityBot, cohere-ai, ChatGPT, GPTBot, OAI-SearchBot, Claude-Web, FacebookBot, Meta-ExternalAgent, Timpibot, omgili, omgilibot Blocking No — crawling allowed
Sitemap: https://variety.com/sitemap_index.xml
Sitemap: https://variety.com/news-sitemap.xml
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php
Disallow: /?s=
Disallow: /*/?s=
Disallow: /search/
Disallow: /search?
Disallow: *?v02
Disallow: *?replytocom
Disallow: /genre/
Disallow: /genre/*
Disallow: /*preview=true
Disallow: /*theme_preview=true

User-agent: anthropic-ai
Disallow: /

User-agent: cohere-ai
Disallow: /

User-agent: omgili
Disallow: /

User-agent: omgilibot
Disallow: /

User-agent: Applebot-Extended
Disallow: /

User-agent: Bytespider
Disallow: /

User-agent: CCBot
Disallow: /

User-agent: ChatGPT-User
Disallow: /

User-agent: ChatGPT
Disallow: /

User-agent: DeepSeek
Disallow: /

User-agent: DeepSeekBot
Disallow: /

User-agent: GPTBot
Disallow: /

User-agent: OAI-SearchBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Claude-Web
Disallow: /

User-agent: Diffbot
Disallow: /

User-agent: FacebookBot
Disallow: /

User-agent: Google-Extended
Disallow: /

User-agent: Meta-ExternalAgent
Disallow: /

User-agent: Meta-ExternalFetcher
Disallow: /

User-agent: PerplexityBot
Disallow: /

User-agent: Timpibot
Disallow: /

User-agent: Webzio-Extended
Disallow: /

User-agent: YouBot
Disallow: /
User-agent: cXensebot
Crawl-delay: 5
sitemap.xml 200 OK
Type Sitemap Index URLs 1380 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
variety.com — via eNom, LLC, 29 years, 11 months old, hosted on WordPress.com (Automattic)
PASS
variety.com — via eNom, LLC, 29 years, 11 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until Sep 16, 2026 (5 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: eNom, LLC
Info::
Hosting: WordPress.com (Automattic)
Got: AS2635
Domain expiry

92 days

September 16, 2026

SSL certificate

81 days

Issued by Let's Encrypt

Domain age

29 years, 11 months

Registered September 17, 1996

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.176

Registrar

eNom, LLC

Lock status unknown 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
Registrar eNom, LLC
Created September 17, 1996 (29 years, 11 months ago)
Expires September 16, 2026 (5 months)
Last Updated September 3, 2025
Name Servers ns-1155.awsdns-16.org, ns-1716.awsdns-22.co.uk, ns-534.awsdns-02.net, ns-74.awsdns-09.com
DNSSEC Not enabled
Hosting
IP Address 192.0.66.176
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.2s)

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 86 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
79 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
1 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
4 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
86 ms
Total Time Total request time from DNS lookup through full response.
87 ms

Connection waterfall

DNS Lookup 79 ms TCP Connect 1 ms TLS Handshake 4 ms Server Processing 2 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