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

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
90
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
B
DNS Records
1 A records, 1 ms lookup
REVIEW
1 A records, 1 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 198.202.211.1
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2620:cb:2000::1
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: cdn.webflow.com
Info::
2 nameserver(s) configured
Got: journey.ns.cloudflare.com, lamar.ns.cloudflare.com
Info::
No MX records — email not configured via DNS
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: 1 ms
Got: 1 ms
A198.202.211.1
AAAA2620:cb:2000::1
CNAMEcdn.webflow.com
NSjourney.ns.cloudflare.com, lamar.ns.cloudflare.com
MX
TXT
CAALookup not available with standard resolver
Resolved in 1 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

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)

B
DNSSEC
Unsigned (DNSSEC not deployed)
REVIEW
Unsigned (DNSSEC not deployed)
Info::
DNSSEC is not deployed
The zone is not DNSSEC-signed. Users on validating resolvers (Cloudflare 1.1.1.1, Quad9 9.9.9.9, growing default in mobile resolvers) get no protection against DNS spoofing for this domain. Most registrars now offer DNSSEC at a single click; consider enabling it for sites where authenticity matters (banking, healthcare, government).
B
CAA Records
No CAA records (any CA may issue certificates)
REVIEW
No CAA records (any CA may issue certificates)
Info::
No CAA records published
Without CAA records, any publicly-trusted CA can issue certificates for this domain. Adding a CAA record (`yourdomain. IN CAA 0 issue "letsencrypt.org"`) restricts issuance to CAs you authorize. Required by CAB Forum baseline since 2017; the default of 'any CA' is widely supported but is the broader attack surface for issuance fraud.
C
Reverse DNS
Action
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR lookup failed for 198.202.211.1: lookup 198.202.211.1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
Info::
PTR lookup failed for 2620:cb:2000::1: lookup 2620:cb:2000::1: no such host
No reverse DNS record set for this IP. Common on bare cloud-VM IPs without provider-side PTR; not a security issue.
B
TLS Certificate Expiry & Recommendations
82 days until leaf cert expires — 4 issues to address
REVIEW

Certificate validity

82
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
Operational Status Page
No status page link detected
REVIEW
No status page link detected
Info::
No operational status page link detected
Status pages communicate planned maintenance and incidents to users -- a hallmark of operationally-mature services. Most SaaS teams publish one via Atlassian Statuspage, Instatus, BetterUptime, or a self-hosted Cachet. Smaller sites legitimately don't need one; flagged as Info, not a failure.
B
Health Check Endpoint
No conventional health endpoint found
REVIEW
No conventional health endpoint found
Info::
No conventional health endpoint found
Health endpoints (/health, /healthz, /status, /ping, /api/health) let uptime monitors, load balancers, and orchestration systems (Kubernetes, ECS, Fly.io) verify the service is alive. Marketing sites and small services often skip them legitimately; flagged as Info, not a failure. Probe results: /api/health: 404, /health: 404, /healthz: 404, /ping: 404, /status: 404.
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 33ms across 3 resolvers (spread 22ms)
PASS
Mean 33ms across 3 resolvers (spread 22ms)
Info::
Cloudflare: 24ms
Got: 24ms via 1.1.1.1:53
Info::
Google: 31ms
Got: 31ms via 8.8.8.8:53
Info::
Quad9: 46ms
Got: 46ms via 9.9.9.9:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.hightolowvoltage.com

https://www.hightolowvoltage.com

43 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.hightolowvoltage.com20043 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2620:cb:2000::1
Got: 17 ms connect
IPv6 Ready
AAAA Records 2620:cb:2000::1 Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 140 URLs
PASS
robots.txt present, sitemap with 140 URLs
Info::
robots.txt is present
Got: 173 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 140 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 173 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /

Disallow: /checkout
Disallow: /paypal-checkout
Disallow: /search
Disallow: /order-confirmation

Sitemap: https://www.hightolowvoltage.com/sitemap.xml
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: www)
Info::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

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

Preferred variant: www

HTTP → HTTPS

301http://www.hightolowvoltage.com/ https://www.hightolowvoltage.com/

Consistent

A+
Domain Intelligence
hightolowvoltage.com — via GoDaddy.com, LLC, 8 years, 1 months old, hosted on Cloudflare
PASS
hightolowvoltage.com — via GoDaddy.com, LLC, 8 years, 1 months old, hosted on Cloudflare
Info::
Domain registered until Sep 15, 2028 (2 years 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: GoDaddy.com, LLC
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: Cloudflare
Got: AS209242
Domain expiry

724 days

September 15, 2028

SSL certificate

82 days

Issued by Google Trust Services

Domain age

8 years, 1 months

Registered September 15, 2018

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS209242

198.202.211.1

Registrar

GoDaddy.com, LLC

Unlocked 2 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 GoDaddy.com, LLC
Created September 15, 2018 (8 years, 1 months ago)
Expires September 15, 2028 (2 years)
Last Updated September 16, 2026
Name Servers ns41.domaincontrol.com, ns42.domaincontrol.com
DNSSEC Not enabled
Hosting
IP Address 198.202.211.1
ASN AS209242 (CLOUDFLARESPECTRUM - Cloudflare London, LLC, US)
Provider Cloudflare
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 42 ms TCP Connect 1 ms TLS Handshake 10 ms Server Processing 46 ms Content Transfer 0 ms
A+
CDN & Delivery
Document on Cloudflare; assets also on Fastly
PASS
Document on Cloudflare; assets also on Fastly
Info::
Document is served via Cloudflare CDN (edge: MAD)
Got: cf-ray: a3e57a177a56ec89-MAD
Info::
CDN cache status: HIT
Info::
Assets on Cloudflare: cdn.prod.website-files.com (assets: 36), cache HIT
Got: cf-ray: a3e57b87fae3137e-CDG
Info::
Assets on Fastly: static.klaviyo.com (assets: 7), cache HIT, HIT
Got: delegation klaviyo-onsite.map.fastly.net
Info::
Assets on Fastly: static-tracking.klaviyo.com (assets: 4), cache HIT, HIT
Got: delegation klaviyo-app.map.fastly.net
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: a3e57a177a56ec89-MAD

Asset hosts on a CDN

  • cdn.prod.website-files.com — Cloudflare · assets: 36 · Cache Status: HIT
  • static.klaviyo.com — Fastly · assets: 7 · Cache Status: HIT, HIT
  • static-tracking.klaviyo.com — Fastly · assets: 4 · Cache Status: HIT, HIT

Other asset hosts

  • www.inventive-acute.com — assets: 4 · Microsoft Azure
  • www.googletagmanager.com — assets: 3 · Google
  • www.gstatic.com — assets: 3 · Google
  • bat.bing.com — assets: 2 · below probe threshold
  • fonts.googleapis.com — assets: 2 · below probe threshold
  • googleads.g.doubleclick.net — assets: 2 · below probe threshold
  • www.clarity.ms — assets: 2 · below probe threshold
  • a.usbrowserspeed.com — assets: 1 · below probe threshold
  • ajax.googleapis.com — assets: 1 · below probe threshold
  • bat.bing.net — assets: 1 · below probe threshold
  • cdn.jsdelivr.net — assets: 1 · below probe threshold
  • d3e54v103j8qbb.cloudfront.net — assets: 1 · below probe threshold
  • js.stripe.com — assets: 1 · below probe threshold
  • s.ksrndkehqnwntyxlhgto.com — assets: 1 · below probe threshold
  • scripts.clarity.ms — assets: 1 · below probe threshold
  • snap.licdn.com — assets: 1 · below probe threshold
  • tag.demandbase.com — assets: 1 · below probe threshold
  • use.typekit.net — assets: 1 · below probe threshold
  • www.google.com — assets: 1 · below probe threshold
A+
CDN Cache Observability
Cache state: HIT
PASS
Cache state: HIT
Info::
CDN cache state observable via 2 header(s)
Got: age=361646, cf-cache-status=HIT
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback