Skip to content
https://vice.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
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.vice.com/
200https://vice.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

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

Consistent

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

Certificate validity

45
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
1 A records, 79 ms lookup
PASS
1 A records, 79 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 192.0.66.177
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
4 nameserver(s) configured
Got: ns-1136.awsdns-14.org, ns-1767.awsdns-28.co.uk, ns-409.awsdns-51.com, ns-851.awsdns-42.net
Info::
5 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: 79 ms
Got: 79 ms
A192.0.66.177
AAAA—
CNAME—
NSns-1136.awsdns-14.org, ns-1767.awsdns-28.co.uk, ns-409.awsdns-51.com, ns-851.awsdns-42.net
MX
1 aspmx.l.google.com
5 alt2.aspmx.l.google.com
5 alt1.aspmx.l.google.com
10 alt4.aspmx.l.google.com
10 alt3.aspmx.l.google.com
TXT
hdm3c44cjhiav30som77bfj86k
site24x7-signals-domain-verification=203dd32b60ef01a9ed6d5f0a2d533127
google-site-verification=2vnKISMVuTAXioui9BB5JRYgkvsjsrNQuTBD6vRdUZI
klaviyo-site-verification=W3ywb2
google-site-verification=UacLp_IBYg9IKcXHq6L2GB9XSn15AIQ0Oq75QZP8J5Y
t2dzyyjjk58zxx4trb2rkmzsq3pm7yt3
google-site-verification=8z8GM9dXL1-EpntXBKm21ItbggUCYcYCdlFItk_eBmA
google-site-verification=0XoBNy3wbp30QiCvylLOm6zYj9kZKVq-MH_VSk9N7YI
zone-ownership-verification-dec629f1cd5e9c0b33ea86958a7648d4d3b07a9fd759332730b3...
atlassian-domain-verification=hskXXsfAYScT3KMiq7xVqeq8pA3Dkwaz5RTPEUtEYuz0g/axla...
_globalsign-domain-verification=FvLwtclLqbuRNqYYejsQKQvAfmnbAsdS6mnPWYJ68i
SPF v=spf1 include:_spf.google.com include:amazonses.com include:servers.mcsv.net in...
_globalsign-domain-verification=FkYUUSU-u5X_D3giiaw10eou45Hypdwsy_sylh2zJu
MS=ms12990789
google-site-verification=lcQiAPONhDm_181jNSi6XpgY0idwd8qpTQH5_q4hQx4
_globalsign-domain-verification=Fw09cFhmPL_-Bfg6BV5_NkyDEkXJfmQd4uPViX560A
d71d927b-d9b1-486d-942d-a63b998cd054
google-site-verification=TratwkuDvIfbfsNT4KG8-YejFfBiW6p4oOcXRxLH3r4
google-site-verification=hmGbIbCrcAR4XY7Pu4PrIOlGhLl8MZ108lr2-5kqguM
_globalsign-domain-verification=cvzudUSBhMY8hRS7IP7p9RJPtfz6pOiqiZnxw4TS3B
MS=ms95705199
google-site-verification=btBMb52eXk6iENlWHf2enS6PXiqmlvh8EKOmYqtcKJI
apple-domain-verification=BOrbQ950ceBMRT6K
google-site-verification=JiCNjfV_KQ9u6p3NdMgJK1bVZmG32BEoMVA8mDJBwNE
MS=ms60645384
facebook-domain-verification=p28ly5dk7y0h9ifoyy14yc3uy9q51m
mk2fh9vmhx7h82rb8fqq1v4fxqtb3dcm
_globalsign-domain-verification=_RbDCFzr-yfROGxWkkSAsoiMH5OQA3bf87X1mVB00o
google-site-verification=v4Zf8BcP9sjIEkb-rLGU3Ac5H9n1PXQGKR1CLzxXCxw
google-site-verification=BuA_rxCVfUoocrJPi9jJBNM-uNdkk7bMiF-pZP_yB1Y
CAALookup not available with standard resolver
Resolved in 79 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

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

https://vice.com

5 ms · HTTP/1.1

301

https://www.vice.com/

568 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://vice.com3015 msHTTP/1.1nginx
2https://www.vice.com/200568 msHTTP/1.1nginx

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 7273 URLs
PASS
robots.txt present, sitemap with 7273 URLs
Info::
robots.txt is present
Got: 260 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 7273 entries
Info::
Sitemap index with 7273 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 260 B Sitemaps referenced 2 User-agents * Blocking No — crawling allowed
# Added by savage robots-txt
# Sitemap archive
Sitemap: https://www.vice.com/sitemap.xml
Sitemap: https://www.vice.com/news-sitemap.xml


# START YOAST BLOCK
# ---------------------------
User-agent: *
Disallow:

# ---------------------------
# END YOAST BLOCK
sitemap.xml 200 OK
Type Sitemap Index URLs 7273 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
vice.com — via Amazon Registrar, Inc., 29 years, 3 months old, hosted on WordPress.com (Automattic)
PASS
vice.com — via Amazon Registrar, Inc., 29 years, 3 months old, hosted on WordPress.com (Automattic)
Info::
Domain registered until May 14, 2029 (3 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: Amazon Registrar, 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: WordPress.com (Automattic)
Got: AS2635
Domain expiry

1062 days

May 14, 2029

SSL certificate

45 days

Issued by Let's Encrypt

Domain age

29 years, 3 months

Registered May 28, 1997

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

WordPress.com (Automattic)

ASN AS2635

192.0.66.177

Registrar

Amazon Registrar, 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 Amazon Registrar, Inc.
Created May 28, 1997 (29 years, 3 months ago)
Expires May 14, 2029 (3 years, 1 months)
Last Updated February 19, 2026
Name Servers ns-1136.awsdns-14.org, ns-1767.awsdns-28.co.uk, ns-409.awsdns-51.com, ns-851.awsdns-42.net
DNSSEC Not enabled
Hosting
IP Address 192.0.66.177
ASN AS2635 (AUTOMATTIC - Automattic, Inc, US)
Provider WordPress.com (Automattic)
Data source: rdap (0.3s)

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 40 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
35 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.
3 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
41 ms
Total Time Total request time from DNS lookup through full response.
41 ms

Connection waterfall

DNS Lookup 35 ms TCP Connect 0 ms TLS Handshake 3 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