Skip to content
https://long-change.mysites.io

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
7
PASS
9
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
9 PASS 7 REVIEW 1 FIX
F
HTTP Probe Timing
Action
Total 8933 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
FIX
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
45 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.
5 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
8.93 s
Total Time Total request time from DNS lookup through full response.
8.93 s

Connection waterfall

DNS Lookup 45 ms TCP Connect 0 ms TLS Handshake 5 ms Server Processing 8.88 s Content Transfer 2 ms
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/1 IPs match cert SAN
REVIEW
0/1 IPs match cert SAN
Info::
PTR lookup failed for 151.101.2.159: lookup 151.101.2.159: 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.
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

C
TLS Certificate Expiry & Recommendations
Action
25 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

25
days left
0d 30d 60d 90d+
Renew soon — under 30 days remaining

Recommended actions

  • Renew certificate — 25 days remaining
  • Enable HSTS: Strict-Transport-Security: max-age=31536000; includeSubDomains
  • Enable DNSSEC on your domain for DNS spoofing protection
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: connection error, /health: connection error, /healthz: connection error, /ping: connection error, /status: connection error.
A
DNS Records
1 A records, 39 ms lookup
PASS
1 A records, 39 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 151.101.2.159
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
No IPv6 (AAAA) records
Info::
No NS records found
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: 39 ms
Got: 39 ms
A151.101.2.159
AAAA—
CNAME—
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 39 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

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)

A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Multi-Resolver DNS Speed
Mean 36ms across 3 resolvers (spread 26ms)
PASS
Mean 36ms across 3 resolvers (spread 26ms)
Info::
Cloudflare: 28ms
Got: 28ms via 1.1.1.1:53
Info::
Google: 28ms
Got: 28ms via 8.8.8.8:53
Info::
Quad9: 54ms
Got: 54ms 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://long-change.mysites.io

https://long-change.mysites.io

6 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://long-change.mysites.io2006 msHTTP/1.1Flywheel/5.1.0
A+
Crawlability
robots.txt present, sitemap with 25 URLs
PASS
robots.txt present, sitemap with 25 URLs
Info::
robots.txt is present
Got: 176 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 25 entries
Info::
Sitemap index with 25 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 176 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
# Default robots file version:2
User-agent: *
Disallow: /calendar/action*
Disallow: /events/action*
Disallow: /cdn-cgi*
Allow: /*.css
Allow: /*.js
Disallow: /*?
Crawl-delay: 3
sitemap.xml 200 OK
Type Sitemap Index URLs 25 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::
HTTP correctly redirects to HTTPS permanently
Got: HTTP 301

www / non-www

https://www.long-change.mysites.io/
200https://long-change.mysites.io/

HTTP → HTTPS

301http://long-change.mysites.io/ → https://long-change.mysites.io/

Consistent

A+
Domain Intelligence
mysites.io — via Tucows Domains Inc., 9 years, 9 months old
PASS
mysites.io — via Tucows Domains Inc., 9 years, 9 months old
Info::
Domain registered until Mar 6, 2027 (3 months remaining)
Info::
Registrar: Tucows Domains 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.
Domain expiry

114 days

March 6, 2027

SSL certificate

25 days

Issued by Sectigo Limited

Domain age

9 years, 9 months

Registered March 6, 2017

DNSSEC

Status unknown

Protects against DNS spoofing

Hosting

Unknown

Registrar

Tucows Domains Inc.

Unlocked 4 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the TLS certificate or verify auto-renewal is working
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Tucows Domains Inc.
Created March 6, 2017 (9 years, 9 months ago)
Expires March 6, 2027 (3 months)
Last Updated August 12, 2026
Name Servers ns-1129.awsdns-13.org, ns-487.awsdns-60.com, ns-959.awsdns-55.net, ns-1990.awsdns-56.co.uk
Registrant REDACTED FOR PRIVACY
Data source: whois (1.5s)

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
CDN & Delivery
Fastly (MISS, MISS)
PASS
Fastly (MISS, MISS)
Info::
Document is served via Fastly CDN (edge: TOJ)
Got: x-served-by: cache-toj-leto2350040-TOJ, cache-toj-leto2350067-TOJ
Info::
CDN cache status: MISS, MISS
Document served via CDN: Fastly
Provider Fastly Cache Status MISS, MISS Evidence x-served-by: cache-toj-leto2350040-TOJ, cache-toj-leto2350067-TOJ
A+
CDN Cache Observability
Cache state: MISS
PASS
Cache state: MISS
Info::
CDN cache state observable via 3 header(s)
Got: x-cache=MISS, MISS, x-cache-hits=0, 0, x-served-by=cache-toj-leto2350040-TOJ, cache-toj-leto2350067-TOJ
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback