Skip to content
https://herotel.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
92
GRADE
A
FIX
0
REVIEW
7
PASS
10
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
10 PASS 7 REVIEW
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 172.66.161.85: lookup 172.66.161.85: 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 104.20.42.13: lookup 104.20.42.13: 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 2606:4700:10::ac42:a155: lookup 2606:4700:10::ac42:a155: 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 2606:4700:10::6814:2a0d: lookup 2606:4700:10::6814:2a0d: 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
HTTP Probe Timing
Total 832 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
REVIEW
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
38 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
17 ms
TLS Handshake TLS Handshake — time to complete the HTTPS encryption handshake.
33 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
781 ms
Total Time Total request time from DNS lookup through full response.
833 ms

Connection waterfall

DNS Lookup 38 ms TCP Connect 17 ms TLS Handshake 33 ms Server Processing 693 ms Content Transfer 52 ms
B
TLS Certificate Expiry & Recommendations
94 days until leaf cert expires — 2 issues to address
REVIEW

Certificate validity

94
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
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
2 A records, 85 ms lookup
PASS
2 A records, 85 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 172.66.161.85, 104.20.42.13
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2606:4700:10::ac42:a155, 2606:4700:10::6814:2a0d
Info::
2 nameserver(s) configured
Got: jim.ns.cloudflare.com, val.ns.cloudflare.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 85 ms
Got: 85 ms
A172.66.161.85, 104.20.42.13
AAAA2606:4700:10::ac42:a155, 2606:4700:10::6814:2a0d
CNAME—
NSjim.ns.cloudflare.com, val.ns.cloudflare.com
MX
5 herotel-com.mail.protection.outlook.com
TXT
MS=ms90148677
SPF v=spf1 ip4:197.189.238.115 ip4:102.37.3.146 ip4:165.73.186.141 ip4:165.73.186.14...
hibp-verify=dweb_ftfjsp6q4s5uci38io8h25ul
everlytic-site-verification=6fb960782b6c34d0f390267747f2908154a7a1e5b6493cb7d974...
7c9cb2a6c866488c93e445306d9cfa1a
anthropic-domain-verification-ensa0j=CQl3ethfeeJttfDAdZrhjgvcD
atlassian-domain-verification=taTh/n/NwdlYoUmp1jyHLmok8oftaI3DBEu80/wSLfuNXg3sCW...
smartsheet-site-validation=DRAf96OE3ytTE3rFpfserxdzv8wIXysz
sophos-domain-verification=214f96c19e4b4ac17e357cfe45f9dde33d3959b571a6064e55483...
surjt6v465u7oo5000eu1pcj2a
google-site-verification=IBoG4 j4Z02yoHaGvUNIUm 7qKCQaGm259s5js5RtDU
google-site-verification=WvnVToqwbyWjyMwypCuNpMh8CCUY_wroWT6-j39kCDk
google-site-verification=EjrgNm3E2l2PZ7wS7FEeOe2jdx-9OZAKXFxiET0DQHg
autodesk-domain-verification=tZtloSDv_6hd7lxbQEaL
CAALookup not available with standard resolver
Resolved in 85 ms
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 24ms across 3 resolvers (spread 11ms)
PASS
Mean 24ms across 3 resolvers (spread 11ms)
Info::
Google: 20ms
Got: 20ms via 8.8.8.8:53
Info::
Cloudflare: 21ms
Got: 21ms via 1.1.1.1:53
Info::
Quad9: 31ms
Got: 31ms 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://herotel.com

https://herotel.com

99 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://herotel.com20099 msHTTP/1.1cloudflare
A+
IPv6 Readiness
IPv6 reachable (17 ms)
PASS
IPv6 reachable (17 ms)
Info::
IPv6 is configured and reachable at 2606:4700:10::ac42:a155, 2606:4700:10::6814:2a0d
Got: 17 ms connect
IPv6 Ready
AAAA Records 2606:4700:10::ac42:a155, 2606:4700:10::6814:2a0d Connection Reachable (17 ms)
A+
Crawlability
robots.txt present, sitemap with 2 URLs
PASS
robots.txt present, sitemap with 2 URLs
Info::
robots.txt is present
Got: 115 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 2 entries
Info::
Sitemap index with 2 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 115 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://herotel.com/sitemap_index.xml
sitemap.xml 200 OK
Type Sitemap Index URLs 2 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.herotel.com/
200https://herotel.com/

HTTP → HTTPS

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

Consistent

A+
Domain Intelligence
herotel.com — via Tucows Domains Inc., 13 years, 5 months old
PASS
herotel.com — via Tucows Domains Inc., 13 years, 5 months old
Info::
Domain registered until Aug 20, 2027 (9 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: 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

279 days

August 20, 2027

SSL certificate

94 days

Issued by GoDaddy.com, Inc.

Domain age

13 years, 5 months

Registered August 20, 2013

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2606:4700:10::ac42:a155

Registrar

Tucows Domains Inc.

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 Tucows Domains Inc.
Created August 20, 2013 (13 years, 5 months ago)
Expires August 20, 2027 (9 months)
Last Updated July 22, 2026
Name Servers jim.ns.cloudflare.com, val.ns.cloudflare.com
DNSSEC Not enabled
Hosting
IP Address 2606:4700:10::ac42:a155
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
CDN & Delivery
Cloudflare (DYNAMIC)
PASS
Cloudflare (DYNAMIC)
Info::
Document is served via Cloudflare CDN (edge: CDG)
Got: cf-ray: a595a802d9226774-CDG
Info::
CDN cache status: DYNAMIC
Document served via CDN: Cloudflare
Provider Cloudflare Cache Status DYNAMIC Evidence cf-ray: a595a802d9226774-CDG
A+
CDN Cache Observability
Cache state: DYNAMIC
PASS
Cache state: DYNAMIC
Info::
CDN cache state observable via 3 header(s)
Got: age=0, cf-cache-status=DYNAMIC, x-cache=MISS
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback