Skip to content
https://videojs.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
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
TLS Certificate Expiry & Recommendations
47 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

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

Recommended actions

  • 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
B
CDN & Delivery
Netlify
REVIEW
Netlify
Info::
Site is served via Netlify CDN
Got: x-nf-request-id: 01KPRZ2A60FS7TWRY18T8R5HPM
CDN Detected: Netlify
Provider Netlify Evidence x-nf-request-id: 01KPRZ2A60FS7TWRY18T8R5HPM
A+
DNS Records
1 A records, 36 ms lookup
PASS
1 A records, 36 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 104.198.14.52
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-1771.awsdns-29.co.uk, ns-1317.awsdns-36.org, ns-1013.awsdns-62.net, ns-13.awsdns-01.com
Info::
7 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: 36 ms
Got: 36 ms
A104.198.14.52
AAAA
CNAME
NSns-1771.awsdns-29.co.uk, ns-1317.awsdns-36.org, ns-1013.awsdns-62.net, ns-13.awsdns-01.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx3.googlemail.com
10 aspmx4.googlemail.com
10 aspmx2.googlemail.com
10 aspmx5.googlemail.com
TXT
SPF v=spf1 include:aspmx.googlemail.com ~all
google-site-verification=QHf9MEYVlEWoNHbzTeUkSQsbRT5Twzqu6N0nX1i3nes
google-site-verification=sHxLPbUY-RiRBDwZBmTpyNRszoYlUrJehEn0G09CcdM
CAALookup not available with standard resolver
Resolved in 36 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), 990 ms total
PASS
1 redirect(s), 990 ms total
Info::
Single redirect
Got: https://videojs.com → https://videojs.org/ (301)
Info::
Redirect overhead: 990 ms total
Got: 990 ms
Info::
Cross-domain redirect detected

https://videojs.com

506 ms · HTTP/1.1

301

https://videojs.org/

484 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://videojs.com301506 msHTTP/1.1Netlify
2https://videojs.org/200484 msHTTP/1.1Netlify

See the visual redirect chain in the HTTP Probe tab →

A+
Crawlability
robots.txt present, sitemap with 1 URLs
PASS
robots.txt present, sitemap with 1 URLs
Info::
robots.txt is present
Got: 62 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 1 entries
Info::
Sitemap index with 1 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 62 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *

Sitemap: https://videojs.org/sitemap-index.xml

sitemap.xml 200 OK
Type Sitemap Index URLs 1 entries Valid XML Yes
A+
URL Variants
www/non-www, trailing slash, HTTP→HTTPS
PASS
www/non-www, trailing slash, HTTP→HTTPS
Info::
www/non-www redirect configured correctly (preferred: non-www)
Info::
HTTP correctly 301-redirects to HTTPS

www / non-www

301https://www.videojs.com/
200https://videojs.com/

Preferred variant: non-www

HTTP → HTTPS

301http://videojs.com/ https://videojs.com/

Consistent

A+
Domain Intelligence
videojs.com — via Amazon Registrar, Inc., 16 years, 2 months old, hosted on Google Cloud
PASS
videojs.com — via Amazon Registrar, Inc., 16 years, 2 months old, hosted on Google Cloud
Info::
Domain registered until Apr 28, 2033 (7 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: Google Cloud
Got: AS396982
Domain expiry

2477 days

April 28, 2033

SSL certificate

47 days

Issued by Let's Encrypt

Domain age

16 years, 2 months

Registered April 28, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Google Cloud

ASN AS396982

104.198.14.52

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 April 28, 2010 (16 years, 2 months ago)
Expires April 28, 2033 (7 years, 1 months)
Last Updated February 11, 2024
Name Servers ns-1013.awsdns-62.net, ns-13.awsdns-01.com, ns-1317.awsdns-36.org, ns-1771.awsdns-29.co.uk
DNSSEC Not enabled
Hosting
IP Address 104.198.14.52
ASN AS396982 (GOOGLE-CLOUD-PLATFORM - Google LLC, US)
Provider Google Cloud
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 541 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
46 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
163 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
166 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
541 ms
Total Time Total request time from DNS lookup through full response.
541 ms

Connection waterfall

DNS Lookup 46 ms TCP Connect 163 ms TLS Handshake 166 ms Server Processing 166 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