Skip to content
https://machineresponse.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
83
GRADE
B
FIX
2
REVIEW
7
PASS
8
INFO
0
Probed from Santa Clara, United States
200 OK
Checks
17
8 PASS 7 REVIEW 2 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: 2a02:4780:84:11b2:b156:3a7a:1085:ce99, 2a02:4780:84:a0a7:6d0f:12d0:ce44:b1b8
Info::
IPv6 connection error
Got: dial tcp6 [2a02:4780:84:11b2:b156:3a7a:1085:ce99]:443: connect: network is unreachable
IPv6 Misconfigured
AAAA Records 2a02:4780:84:11b2:b156:3a7a:1085:ce99, 2a02:4780:84:a0a7:6d0f:12d0:ce44:b1b8 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)

D
CDN & Delivery
Action
No CDN detected
FIX
No CDN detected
Warning::
No CDN detected
A CDN can significantly improve load times for users around the world by caching content at edge nodes closer to them.
No CDN detected

Consider using a CDN to improve global delivery speed and reduce origin load.

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/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR lookup failed for 147.79.120.199: lookup 147.79.120.199: 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 92.112.198.123: lookup 92.112.198.123: 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 2a02:4780:84:11b2:b156:3a7a:1085:ce99: lookup 2a02:4780:84:11b2:b156:3a7a:1085:ce99: 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 2a02:4780:84:a0a7:6d0f:12d0:ce44:b1b8: lookup 2a02:4780:84:a0a7:6d0f:12d0:ce44:b1b8: 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
Multi-Resolver DNS Speed
Mean 104ms across 3 resolvers (spread 113ms)
REVIEW
Mean 104ms across 3 resolvers (spread 113ms)
Info::
Google: 60ms
Got: 60ms via 8.8.8.8:53
Info::
Quad9: 81ms
Got: 81ms via 9.9.9.9:53
Info::
Cloudflare: 173ms
Got: 173ms via 1.1.1.1:53
B
TLS Certificate Expiry & Recommendations
70 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

70
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
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+
DNS Records
2 A records, 168 ms lookup
PASS
2 A records, 168 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 147.79.120.199, 92.112.198.123
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:4780:84:11b2:b156:3a7a:1085:ce99, 2a02:4780:84:a0a7:6d0f:12d0:ce44:b1b8
Info::
2 nameserver(s) configured
Got: ns1.dns-parking.com, ns2.dns-parking.com
Info::
2 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 168 ms
Got: 168 ms
A147.79.120.199, 92.112.198.123
AAAA2a02:4780:84:11b2:b156:3a7a:1085:ce99, 2a02:4780:84:a0a7:6d0f:12d0:ce44:b1b8
CNAME—
NSns1.dns-parking.com, ns2.dns-parking.com
MX
5 mx1.hostinger.com
10 mx2.hostinger.com
TXT
SPF v=spf1 include:_spf.mail.hostinger.com ~all
CAALookup not available with standard resolver
Resolved in 168 ms
A+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
No CNAME record present
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://machineresponse.com

https://machineresponse.com

1035 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://machineresponse.com2001035 msHTTP/1.1hcdn
A+
Crawlability
robots.txt present, sitemap with 3 URLs
PASS
robots.txt present, sitemap with 3 URLs
Info::
robots.txt is present
Got: 140 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 3 entries
Info::
Sitemap index with 3 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 140 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php

User-agent: *

Disallow: /wp-admin/

Allow: /wp-admin/admin-ajax.php
sitemap.xml 200 OK
Type Sitemap Index URLs 3 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.machineresponse.com/
200https://machineresponse.com/

Preferred variant: non-www

HTTP → HTTPS

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

Consistent

A
Domain Intelligence
machineresponse.com — via Spaceship, Inc., 2 years, 11 months old, hosted on Hostinger
PASS
machineresponse.com — via Spaceship, Inc., 2 years, 11 months old, hosted on Hostinger
Warning::
Domain expires in 34 days
Consider enabling auto-renewal to prevent accidental expiration.
Got: Expires Sep 3, 2026
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: Spaceship, 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: Hostinger
Got: AS47583
Domain expiry

25 days

September 3, 2026

SSL certificate

70 days

Issued by Let's Encrypt

Domain age

2 years, 11 months

Registered September 3, 2023

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Hostinger

ASN AS47583

84.32.84.174

Registrar

Spaceship, Inc.

Unlocked 2 NS records
Expiry timeline
Today
+1 year
Domain expiry SSL expiry Danger zone (≤30 days)
Recommended actions
  • Renew the domain or enable auto-renewal to prevent accidental expiry
  • Enable DNSSEC to protect visitors from DNS spoofing
  • Enable registrar lock (clientTransferProhibited) to block unauthorized domain transfers
Registrar Spaceship, Inc.
Created September 3, 2023 (2 years, 11 months ago)
Expires September 3, 2026 (1 months)
Last Updated September 12, 2025
Name Servers ns1.dns-parking.com, ns2.dns-parking.com
DNSSEC Not enabled
Hosting
IP Address 84.32.84.174
ASN AS47583 (AS-HOSTINGER - Hostinger International Limited, CY)
Provider Hostinger
Data source: rdap (0.2s)

Consider enabling auto-renewal to prevent accidental expiration.

Why this matters

Domain expiry approaching — renew immediately and ensure auto-renew + alerting are configured.

Source: ICANN renewal policy

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

Connection waterfall

DNS Lookup 181 ms TCP Connect 25 ms TLS Handshake 30 ms Server Processing 25 ms Content Transfer 37 ms
A+
CDN Cache Observability
Cache state: Age=337185s
PASS
Cache state: Age=337185s
Info::
CDN cache state observable via 1 header(s)
Got: age=337185
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback