Skip to content
https://www.roseninns.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
91
GRADE
A
FIX
0
REVIEW
9
PASS
8
INFO
0
Probed from Madrid, Spain
200 OK
Checks
17
8 PASS 9 REVIEW
B
DNS Records
2 A records, 34 ms lookup
REVIEW
2 A records, 34 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 84.53.132.67, 72.247.155.96
Info::
Has 2 IPv6 (AAAA) record(s)
Got: 2a02:26f0:980:f::214:fd61, 2a02:26f0:980:f::214:fd52
Warning::
CNAME record at zone apex
A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.
Got: www-roseninns-com.galaxy.tf
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: 34 ms
Got: 34 ms
A84.53.132.67, 72.247.155.96
AAAA2a02:26f0:980:f::214:fd61, 2a02:26f0:980:f::214:fd52
CNAMEwww-roseninns-com.galaxy.tf
NS—
MX—
TXT—
CAALookup not available with standard resolver
Resolved in 34 ms

A CNAME at the zone apex can break MX and NS records. Use ALIAS/ANAME or A records instead.

Why this matters

CNAME at the apex (example.com) breaks every other apex record (MX, TXT, NS) — DNS-protocol violation per RFC 1034.

Learn more ▾

RFC 1034 forbids CNAME alongside other records at the same name. Some DNS providers offer ALIAS / ANAME / flattened-CNAME records that work around this — use those instead. Otherwise apex-level CNAME breaks email (no MX), domain ownership verification (no TXT), and more.

Source: RFC 1034

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)

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.
B
Reverse DNS
0/4 IPs match cert SAN
REVIEW
0/4 IPs match cert SAN
Info::
PTR for 84.53.132.67 does not match any cert SAN: a84-53-132-67.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 72.247.155.96 does not match any cert SAN: a72-247-155-96.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a02:26f0:980:f::214:fd61 does not match any cert SAN: g2a02-26f0-0980-000f-0000-0000-0214-fd61.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
Info::
PTR for 2a02:26f0:980:f::214:fd52 does not match any cert SAN: g2a02-26f0-0980-000f-0000-0000-0214-fd52.deploy.static.akamaitechnologies.com
Common when behind a CDN or shared hosting (PTR points at the provider's hostname). Mismatch can also affect mail deliverability if this IP sends email -- many MTAs reject mail when forward+reverse DNS disagree.
B
TLS Certificate Expiry & Recommendations
75 days until leaf cert expires — 3 issues to address
REVIEW

Certificate validity

75
days left
0d 30d 60d 90d+

Recommended actions

  • Submit your domain to hstspreload.org to be added to the Chrome preload list
  • 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
Document on AWS CloudFront; assets also on Akamai
REVIEW
Document on AWS CloudFront; assets also on Akamai
Info::
Document is served via AWS CloudFront CDN (edge: MAD56-P6)
Got: x-amz-cf-id: njCNAtVft5lMxkrN1BVqKlYSUk57gPsTsbN13me6nY73-5Ww1RcATQ==
Info::
Assets on Akamai: image-tc.galaxy.tf (assets: 38)
Got: delegation galaxy-dd.edgesuite.net
Document served via CDN: AWS CloudFront
Provider AWS CloudFront Evidence x-amz-cf-id: njCNAtVft5lMxkrN1BVqKlYSUk57gPsTsbN13me6nY73-5Ww1RcATQ==

Asset hosts on a CDN

  • image-tc.galaxy.tf — Akamai · assets: 38

Other asset hosts

  • fonts.googleapis.com — assets: 8 · Google
  • www.googletagmanager.com — assets: 5 · Google
  • app.secureprivacy.ai — assets: 1 · below probe threshold
  • cmp.secureprivacy.ai — assets: 1 · below probe threshold
B
CDN Cache Observability
No CDN cache-status headers in the response
REVIEW
No CDN cache-status headers in the response
Info::
No CDN cache-status headers in the response
Without an X-Cache / CF-Cache-Status / X-Vercel-Cache / Age header, you can't tell from outside whether a request hit the cache or went to origin. Operationally important: enables debugging stale-content reports and verifying cache rules. Most managed CDN platforms emit at least one of these by default; absence often means the platform's diagnostic headers are stripped at an upstream proxy.
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+
Subdomain Takeover
No subdomain takeover risk detected
PASS
No subdomain takeover risk detected
Info::
CNAME does not point at a known takeover-able service
A+
Multi-Resolver DNS Speed
Mean 47ms across 3 resolvers (spread 43ms)
PASS
Mean 47ms across 3 resolvers (spread 43ms)
Info::
Quad9: 26ms
Got: 26ms via 9.9.9.9:53
Info::
Google: 48ms
Got: 48ms via 8.8.8.8:53
Info::
Cloudflare: 69ms
Got: 69ms via 1.1.1.1:53
A+
Redirect Chain
No redirects — direct access
PASS
No redirects — direct access
Info::
No redirects — direct access
Got: https://www.roseninns.com

https://www.roseninns.com

55 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://www.roseninns.com20055 msHTTP/1.1GLXD-AKA
A+
IPv6 Readiness
IPv6 reachable (0 ms)
PASS
IPv6 reachable (0 ms)
Info::
IPv6 is configured and reachable at 2a02:26f0:980:f::214:fd61, 2a02:26f0:980:f::214:fd52
Got: 0 ms connect
IPv6 Ready
AAAA Records 2a02:26f0:980:f::214:fd61, 2a02:26f0:980:f::214:fd52 Connection Reachable (0 ms)
A+
Crawlability
robots.txt present, sitemap with 196 URLs
PASS
robots.txt present, sitemap with 196 URLs
Info::
robots.txt is present
Got: 72 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 196 entries
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 72 B Sitemaps referenced 1 User-agents * Blocking No — crawling allowed
User-agent: *
Disallow:

Sitemap: https://www.roseninns.com/sitemap.xml
sitemap.xml 200 OK
Type URL Set URLs 196 entries Valid XML Yes
Sample URLs:
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: www)
Warning::
HTTP→HTTPS redirect is not permanent
Got: HTTP 302 Expected: 301 or 308 permanent redirect

www / non-www

200https://www.roseninns.com/
301https://roseninns.com/

Preferred variant: www

HTTP → HTTPS

302http://www.roseninns.com/ → https://www.roseninns.com/

Use a permanent redirect (301 or 308) instead of a temporary one

A+
Domain Intelligence
roseninns.com — via Network Solutions, LLC, 16 years, 5 months old, hosted on AWS
PASS
roseninns.com — via Network Solutions, LLC, 16 years, 5 months old, hosted on AWS
Info::
Domain registered until Jul 22, 2028 (1 years, 10 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: Network Solutions, 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: AWS
Got: AS16509
Domain expiry

656 days

July 22, 2028

SSL certificate

75 days

Issued by Let's Encrypt

Domain age

16 years, 5 months

Registered July 22, 2010

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

15.197.68.234

Registrar

Network Solutions, 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 Network Solutions, LLC
Created July 22, 2010 (16 years, 5 months ago)
Expires July 22, 2028 (1 years, 10 months)
Last Updated July 17, 2023
Name Servers ns15.worldnic.com, ns16.worldnic.com
DNSSEC Not enabled
Hosting
IP Address 15.197.68.234
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.3s)

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 280 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
76 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.
7 ms
Time to First Byte Time to First Byte — how long the server takes to respond with the first byte of data.
279 ms
Total Time Total request time from DNS lookup through full response.
281 ms

Connection waterfall

DNS Lookup 76 ms TCP Connect 0 ms TLS Handshake 7 ms Server Processing 196 ms Content Transfer 1 ms
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback