Skip to content
https://siteorigin.com

Infrastructure

· 9 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
1
PASS
7
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
9
7 PASS 1 REVIEW 1 FIX
F
IPv6 Readiness
Action
IPv6 records exist but unreachable
FIX
IPv6 records exist but unreachable
Warning::
IPv6 DNS records exist but server is not reachable
Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.
Got: 2606:4700:20::681a:af1, 2606:4700:20::681a:bf1, 2606:4700:20::ac43:4561
Info::
IPv6 connection error
Got: dial tcp6 [2606:4700:20::681a:af1]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2606:4700:20::681a:af1, 2606:4700:20::681a:bf1, 2606:4700:20::ac43:4561 Connection UNREACHABLE

Having AAAA records but an unreachable server is worse than no AAAA — clients may experience delays before falling back to IPv4.

Why this matters

Advertising IPv6 (AAAA records) without a reachable server means IPv6-preferring clients silently fail every connection.

Learn more ▾

Modern browsers prefer IPv6 if AAAA exists (Happy Eyeballs algorithm). If the IPv6 server isn't reachable, browsers fall back to IPv4 — but with seconds of added latency per request. Either fix IPv6 reachability or remove the AAAA records.

Source: RFC 8305 (Happy Eyeballs)

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

Certificate validity

89
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
3 A records, 11 ms lookup
PASS
3 A records, 11 ms lookup
Info::
Resolves to 3 IPv4 address(es)
Got: 104.26.11.241, 104.26.10.241, 172.67.69.97
Info::
Has 3 IPv6 (AAAA) record(s)
Got: 2606:4700:20::681a:af1, 2606:4700:20::681a:bf1, 2606:4700:20::ac43:4561
Info::
2 nameserver(s) configured
Got: noah.ns.cloudflare.com, pam.ns.cloudflare.com
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: 11 ms
Got: 11 ms
A104.26.11.241, 104.26.10.241, 172.67.69.97
AAAA2606:4700:20::681a:af1, 2606:4700:20::681a:bf1, 2606:4700:20::ac43:4561
CNAME—
NSnoah.ns.cloudflare.com, pam.ns.cloudflare.com
MX
1 aspmx.l.google.com
5 alt1.aspmx.l.google.com
5 alt2.aspmx.l.google.com
10 aspmx2.googlemail.com
10 aspmx3.googlemail.com
TXT
brevo-code:7559062aecbeb25467e6d9873263ec62
google-site-verification=ACKdg-UQfELvaS1hhERS1K9yfwaYGxcjt077bb5nxmo
google-site-verification=ZEX3k1ET1MCluvmNcPNJAGT2L1--2USBVQQo7jtPyEU
SPF v=spf1 mx a ?all
CAALookup not available with standard resolver
Resolved in 11 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
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://siteorigin.com

https://siteorigin.com

46 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://siteorigin.com20046 msHTTP/1.1cloudflare
A+
Crawlability
robots.txt present, sitemap with 43 URLs
PASS
robots.txt present, sitemap with 43 URLs
Info::
robots.txt is present
Got: 155 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 43 entries
Info::
Sitemap index with 43 child sitemaps
Info::
robots.txt does not reference a sitemap
Add a 'Sitemap:' directive to robots.txt so search engines can discover your sitemap.

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 155 B Sitemaps referenced 0 User-agents *, Googlebot, Bingbot Blocking No — crawling allowed
User-agent: *
Disallow: /wp-json/
Disallow: /wp-login.php
Disallow: /wp-admin/

User-agent: Googlebot
Allow: /thread/

User-agent: Bingbot
Allow: /thread/
sitemap.xml 200 OK
Type Sitemap Index URLs 43 entries Valid XML Yes
Child Sitemaps:
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.siteorigin.com/
200https://siteorigin.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
siteorigin.com — via GoDaddy.com, LLC, 22 years, 3 months old, hosted on Cloudflare
PASS
siteorigin.com — via GoDaddy.com, LLC, 22 years, 3 months old, hosted on Cloudflare
Info::
Domain registered until Apr 27, 2030 (4 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: AS13335
Domain expiry

1414 days

April 27, 2030

SSL certificate

89 days

Issued by Google Trust Services

Domain age

22 years, 3 months

Registered April 27, 2004

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Cloudflare

ASN AS13335

104.26.11.241

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 April 27, 2004 (22 years, 3 months ago)
Expires April 27, 2030 (4 years)
Last Updated September 2, 2022
Name Servers noah.ns.cloudflare.com, pam.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 104.26.11.241
ASN AS13335 (CLOUDFLARENET - Cloudflare, Inc., US)
Provider Cloudflare
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

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 38 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
9 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.
38 ms
Total Time Total request time from DNS lookup through full response.
38 ms

Connection waterfall

DNS Lookup 9 ms TCP Connect 2 ms TLS Handshake 9 ms Server Processing 17 ms Content Transfer 1 ms
A+
CDN & Delivery
Cloudflare (HIT)
PASS
Cloudflare (HIT)
Info::
Site is served via Cloudflare CDN (edge: SJC)
Got: cf-ray: 9f0020f8f8d7be62-SJC
Info::
CDN cache status: HIT
CDN Detected: Cloudflare
Provider Cloudflare Cache Status HIT Evidence cf-ray: 9f0020f8f8d7be62-SJC
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback