Skip to content
https://roma.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
86
GRADE
B
FIX
2
REVIEW
8
PASS
7
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
7 PASS 8 REVIEW 2 FIX
D
URL Variants
Action
www/non-www, trailing slash, HTTP→HTTPS
FIX
www/non-www, trailing slash, HTTP→HTTPS
Critical::
Both www and non-www versions serve content
Got: Both variants return 200 Expected: One variant 301-redirects to the other
Critical::
HTTP version does not redirect to HTTPS
Got: HTTP 0 Expected: 301 redirect to HTTPS

www / non-www

200https://www.roma.com/
200https://roma.com/

Inconsistent — duplicate content risk

HTTP → HTTPS

http://roma.com/

HTTP version does not redirect to HTTPS

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.
B
Reverse DNS
0/2 IPs match cert SAN
REVIEW
0/2 IPs match cert SAN
Info::
PTR for 78.46.4.191 does not match any cert SAN: dedi1491.your-server.de
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 2a01:4f8:d0a:23de::2 does not match any cert SAN: dedi1491.your-server.de
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
Redirect Chain
1 redirect(s), 1221 ms total
REVIEW
1 redirect(s), 1221 ms total
Info::
Single redirect
Got: https://roma.com → https://www.roma.com/ (301)
Info::
WWW normalization redirect
Warning::
Redirect overhead: 1221 ms total
Got: 1221 ms

https://roma.com

547 ms · HTTP/1.1

301

https://www.roma.com/

674 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://roma.com301547 msHTTP/1.1Apache
2https://www.roma.com/200674 msHTTP/1.1Apache

See the visual redirect chain in the HTTP Probe tab →

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

Certificate validity

109
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
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: connection error, /health: connection error, /healthz: connection error, /ping: 404, /status: connection error.
A+
DNS Records
1 A records, 43 ms lookup
PASS
1 A records, 43 ms lookup
Info::
Resolves to 1 IPv4 address(es)
Got: 78.46.4.191
Info::
Single A record — no DNS redundancy
Multiple A records provide failover if one server goes down.
Info::
Has 1 IPv6 (AAAA) record(s)
Got: 2a01:4f8:d0a:23de::2
Info::
3 nameserver(s) configured
Got: ns1.your-server.de, ns.second-ns.com, ns3.second-ns.de
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 43 ms
Got: 43 ms
A78.46.4.191
AAAA2a01:4f8:d0a:23de::2
CNAME—
NSns1.your-server.de, ns.second-ns.com, ns3.second-ns.de
MX
10 dedi1491.your-server.de
TXT
google-site-verification=gNRXWqk1ePxXg4x1pM14mkXIRMGhYxZxn8kFlI83iIg
SPF v=spf1 +a +mx ?all
facebook-domain-verification=vxrs1dxalpbwhxkif9skzys6xh8kw6
CAALookup not available with standard resolver
Resolved in 43 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

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 44ms across 3 resolvers (spread 38ms)
PASS
Mean 44ms across 3 resolvers (spread 38ms)
Info::
Google: 19ms
Got: 19ms via 8.8.8.8:53
Info::
Cloudflare: 56ms
Got: 56ms via 1.1.1.1:53
Info::
Quad9: 57ms
Got: 57ms via 9.9.9.9:53
A+
IPv6 Readiness
IPv6 reachable (28 ms)
PASS
IPv6 reachable (28 ms)
Info::
IPv6 is configured and reachable at 2a01:4f8:d0a:23de::2
Got: 28 ms connect
IPv6 Ready
AAAA Records 2a01:4f8:d0a:23de::2 Connection Reachable (28 ms)
A+
Crawlability
robots.txt present, sitemap with 10 URLs
PASS
robots.txt present, sitemap with 10 URLs
Info::
robots.txt is present
Got: 288 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 10 entries
Info::
Sitemap index with 10 child sitemaps
Info::
robots.txt references sitemap
robots.txt 200 OK
Size 288 B Sitemaps referenced 1 User-agents facebookexternalhit, meta-externalagent, * Blocking No — crawling allowed
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.roma.com/sitemap_index.xml

#WP Import Export Rule
User-agent: *
Disallow: /wp-content/uploads/vj-wp-import-export/

User-agent: facebookexternalhit 
Allow: /

User-agent: meta-externalagent
Allow: /
sitemap.xml 200 OK
Type Sitemap Index URLs 10 entries Valid XML Yes
Child Sitemaps:
A+
Domain Intelligence
roma.com — via Network Solutions, LLC, 31 years, 9 months old
PASS
roma.com — via Network Solutions, LLC, 31 years, 9 months old
Info::
Domain registered until May 15, 2029 (2 years, 8 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.
Domain expiry

984 days

May 15, 2029

SSL certificate

109 days

Issued by DigiCert Inc

Domain age

31 years, 9 months

Registered May 14, 1995

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

Unknown

2a01:4f8:d0a:23de::2

Registrar

Network Solutions, LLC

Unlocked 3 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 May 14, 1995 (31 years, 9 months ago)
Expires May 15, 2029 (2 years, 8 months)
Last Updated November 30, 2024
Name Servers ns.second-ns.com, ns1.your-server.de, ns3.second-ns.de
DNSSEC Not enabled
Hosting
IP Address 2a01:4f8:d0a:23de::2
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 568 ms — DNS, TCP, TLS, TTFB, content transfer breakdown
PASS
DNS Lookup DNS Lookup — time to resolve the domain name to an IP address.
43 ms
TCP Connect TCP Connect — time to establish a TCP connection to the server.
28 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.
569 ms
Total Time Total request time from DNS lookup through full response.
569 ms

Connection waterfall

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

Send Feedback