Skip to content
https://leadconnectorhq.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
3
PASS
6
INFO
0
Probed from New York, United Stated
301 Moved Permanently
Checks
9
6 PASS 3 REVIEW
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.leadconnectorhq.com/
200https://leadconnectorhq.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

301http://leadconnectorhq.com/ https://leadconnectorhq.com

Consistent

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

Certificate validity

79
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
B
CDN & Delivery
Cloudflare
REVIEW
Cloudflare
Info::
Site is served via Cloudflare CDN (edge: EWR)
Got: cf-ray: 9effb86f19b42732-EWR
CDN Detected: Cloudflare
Provider Cloudflare Evidence cf-ray: 9effb86f19b42732-EWR
A+
DNS Records
2 A records, 9 ms lookup
PASS
2 A records, 9 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 104.18.34.38, 172.64.153.218
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a06:98c1:3106::ac40:99da, 2606:4700:440c::6812:2226
Info::
2 nameserver(s) configured
Got: megan.ns.cloudflare.com, noah.ns.cloudflare.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
Info::
DNS resolution time: 9 ms
Got: 9 ms
A104.18.34.38, 172.64.153.218
AAAA2a06:98c1:3106::ac40:99da, 2606:4700:440c::6812:2226
CNAME
NSmegan.ns.cloudflare.com, noah.ns.cloudflare.com
MX
10 aspmx.l.google.com
TXT
MS=ADD55F3518975470D19277C461F062370FF60090
google-site-verification=C_9r5UlUN06eyL8u1_3BB_6l2R7RadM4UtDvgwWi068
google-site-verification=G2zhuimvi8SLlQSI_aj4cIQQZM_80pOy-DsEchntuf8
google-site-verification=Lhy0RYNwuf1fISdR0F0k7wcDgPKRGgc9q330q61cZYg
google-site-verification=TictMSf7gzEW0sRRf5Hmf-lgMnAFs9b5y2OlML82eIM
google-site-verification=bRyZ93rolDbRUMqA62Jy3iUBW_EWasZOEcCKa1iIHeY
google-site-verification=h6gYTbHPXIxk-lvnrIv3oDToG0RDAi2rTc8ETsuVnfM
google-site-verification=tNTw6on3UyLgv5QB3Wr1NnF5XNVHC2TZew6_b-bN0cE
google-site-verification=uAEgKCv2YSMSAUdSq6xm81DYwqOLVA-iEtS43lvY0fc
SPF v=spf1 include:mailgun.org include:_spf.google.com ~all
CAALookup not available with standard resolver
Resolved in 9 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.

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

https://leadconnectorhq.com

37 ms · HTTP/1.1

301

https://www.leadconnectorhq.com/

168 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://leadconnectorhq.com30137 msHTTP/1.1cloudflare
2https://www.leadconnectorhq.com/200168 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

A+
IPv6 Readiness
IPv6 reachable (1 ms)
PASS
IPv6 reachable (1 ms)
Info::
IPv6 is configured and reachable at 2a06:98c1:3106::ac40:99da, 2606:4700:440c::6812:2226
Got: 1 ms connect
IPv6 Ready
AAAA Records 2a06:98c1:3106::ac40:99da, 2606:4700:440c::6812:2226 Connection Reachable (1 ms)
A
Crawlability
robots.txt present, sitemap with 0 URLs
PASS
robots.txt present, sitemap with 0 URLs
Info::
robots.txt is present
Got: 0 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Warning::
sitemap.xml is empty — no URLs found
An empty sitemap provides no value. Add <url> entries for your pages.
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

An empty sitemap provides no value. Add <url> entries for your pages.

Why this matters

An empty sitemap signals 'no content to index' to Google — actively harmful versus having no sitemap at all.

Learn more

Google compares URLs in the sitemap against URLs it has crawled. An empty sitemap on a site with thousands of pages signals abandonment. Either populate it correctly (most CMSes auto-generate) or delete the file and let Google crawl normally.

Source: Google Search Central / sitemaps.org

Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

Why this matters

robots.txt omits Sitemap: directive — crawlers must fetch /sitemap.xml by convention; reliable but missing the explicit hint.

Source: sitemaps.org

robots.txt 200 OK
Size 0 B Sitemaps referenced 0 User-agents Blocking No — crawling allowed
sitemap.xml 200 OK
Type URL Set URLs 0 entries Valid XML Yes
A+
Domain Intelligence
leadconnectorhq.com — via GoDaddy.com, LLC, 5 years, 6 months old
PASS
leadconnectorhq.com — via GoDaddy.com, LLC, 5 years, 6 months old
Info::
Domain registered until Oct 23, 2027 (1 years, 6 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: 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.
Domain expiry

468 days

October 23, 2027

SSL certificate

79 days

Issued by Google Trust Services

Domain age

5 years, 6 months

Registered October 23, 2020

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a06:98c1:3106::ac40:99da

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 October 23, 2020 (5 years, 6 months ago)
Expires October 23, 2027 (1 years, 6 months)
Last Updated October 9, 2024
Name Servers megan.ns.cloudflare.com, noah.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2a06:98c1:3106::ac40:99da
Data source: rdap (0.0s)

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

Connection waterfall

DNS Lookup 5 ms TCP Connect 2 ms TLS Handshake 9 ms Server Processing 12 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