Skip to content
https://asroma.com

Infrastructure

· 17 checks — DNS, redirects, IPv6, crawlability, URL variants, and domain intelligence rolled into one auditable list.
SCORE
87
GRADE
B
FIX
1
REVIEW
8
PASS
8
INFO
0
Probed from Madrid, Spain
301 Moved Permanently
Checks
17
8 PASS 8 REVIEW 1 FIX
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 99.83.231.86 does not match any cert SAN: a6becf9f9a1ecabe0.awsglobalaccelerator.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 75.2.77.125 does not match any cert SAN: a6becf9f9a1ecabe0.awsglobalaccelerator.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
Redirect Chain
2 redirect(s), 420 ms total
REVIEW
2 redirect(s), 420 ms total
Warning::
2 redirects before reaching final URL
Each redirect adds latency. Try to minimize the chain to 1 hop.
Info::
WWW normalization redirect
Info::
Uses 302 (temporary) redirect
If permanent, use 301 instead.
Got: https://www.asroma.com:443/

https://asroma.com

98 ms · HTTP/1.1

301

https://www.asroma.com:443/

162 ms · HTTP/1.1

302

https://www.asroma.com/en

160 ms · HTTP/1.1 FINAL

#URLStatusTimeProtocolServer
1https://asroma.com30198 msHTTP/1.1awselb/2.0
2https://www.asroma.com:443/302162 msHTTP/1.1CloudFront
3https://www.asroma.com/en200160 msHTTP/1.1

See the visual redirect chain in the HTTP Probe tab →

Each redirect adds latency. Try to minimize the chain to 1 hop.

Why this matters

Redirect chain — each hop adds latency; combine into one redirect where possible.

Source: Google Search Central / web.dev

If permanent, use 301 instead.

Why this matters

302 (Found) is for genuinely temporary redirects — if this redirect is permanent, switch to 301 to preserve SEO equity.

Learn more ▾

Search engines treat 302 as temporary, keeping the original URL indexed and not transferring full link equity to the destination. Use 301 (Moved Permanently) for permanent redirects (HTTP→HTTPS, www-vs-non-www, URL restructures).

Source: Google Search Central

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

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

Certificate validity

137
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
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.
A+
DNS Records
2 A records, 38 ms lookup
PASS
2 A records, 38 ms lookup
Info::
Resolves to 2 IPv4 address(es)
Got: 99.83.231.86, 75.2.77.125
Info::
No IPv6 (AAAA) records
Info::
5 nameserver(s) configured
Got: ns0.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns3.dnsmadeeasy.com
Info::
1 mail exchanger(s) configured
Info::
SPF record present in TXT
Info::
DNS resolution time: 38 ms
Got: 38 ms
A99.83.231.86, 75.2.77.125
AAAA—
CNAME—
NSns0.dnsmadeeasy.com, ns4.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns3.dnsmadeeasy.com
MX
0 asroma-com.mail.protection.outlook.com
TXT
fastly-domain-delegation-vpcD1yI3tte43B2K1pDY-367790-2021-05-11
google-site-verification=PHYcarqwkCiDV_ercfqKxN97lleBP_3FbY9Ck_jwVzs
5i2gprskimbiu8hdoadqmcqdlr
SPF v=spf1 include:spf.protection.outlook.com include:_spf1.swapcard.com include:spf...
_globalsign-domain-verification=2wRqY6IrIINLY7B8Qcp-qur9HsiRTO04g4gwsMmFy3
8rg0tcthvoq1ul7ukjccnmoujv
MS=ms61342963
CAALookup not available with standard resolver
Resolved in 38 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 22ms across 3 resolvers (spread 5ms)
PASS
Mean 22ms across 3 resolvers (spread 5ms)
Info::
Quad9: 20ms
Got: 20ms via 9.9.9.9:53
Info::
Cloudflare: 21ms
Got: 21ms via 1.1.1.1:53
Info::
Google: 25ms
Got: 25ms via 8.8.8.8:53
A+
Crawlability
robots.txt present, sitemap with 290 URLs
PASS
robots.txt present, sitemap with 290 URLs
Info::
robots.txt is present
Got: 240 bytes
Info::
sitemap.xml is present
Info::
sitemap.xml is valid XML
Info::
sitemap.xml contains 290 entries
Info::
Sitemap index with 290 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 240 B Sitemaps referenced 0 User-agents * Blocking No — crawling allowed
User-agent: *
Allow: /
Disallow: /it/biglietti/lupacchiotti-in-campo
Disallow: /it/biglietti/business-club-app
Disallow: /it/biglietti/romamor-hospitality
Disallow: /en/search
Disallow: /it/cerca
Disallow: /en/search?*
Disallow: /it/cerca?*
sitemap.xml 200 OK
Type Sitemap Index URLs 290 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 redirects to HTTPS permanently
Got: HTTP 301

www / non-www

302https://www.asroma.com/
200https://asroma.com/

Preferred variant: non-www

HTTP → HTTPS

301http://asroma.com/ → https://www.asroma.com:443/

Consistent

A+
Domain Intelligence
asroma.com — via eNom, LLC, 24 years, 9 months old, hosted on AWS
PASS
asroma.com — via eNom, LLC, 24 years, 9 months old, hosted on AWS
Info::
Domain registered until Mar 24, 2027 (7 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: eNom, 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

210 days

March 24, 2027

SSL certificate

137 days

Issued by Amazon

Domain age

24 years, 9 months

Registered March 24, 2002

DNSSEC

Not enabled

Protects against DNS spoofing

Hosting

AWS

ASN AS16509

75.2.77.125

Registrar

eNom, LLC

Unlocked 5 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 eNom, LLC
Created March 24, 2002 (24 years, 9 months ago)
Expires March 24, 2027 (7 months)
Last Updated March 23, 2026
Name Servers ns0.dnsmadeeasy.com, ns1.dnsmadeeasy.com, ns2.dnsmadeeasy.com, ns3.dnsmadeeasy.com, ns4.dnsmadeeasy.com
DNSSEC Not enabled
Hosting
IP Address 75.2.77.125
ASN AS16509 (AMAZON-02 - Amazon.com, Inc., US)
Provider AWS
Data source: rdap (0.4s)

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

Connection waterfall

DNS Lookup 35 ms TCP Connect 1 ms TLS Handshake 64 ms Server Processing 32 ms Content Transfer 0 ms
A+
Health Check Endpoint
Health endpoint at https://asroma.com/api/health (HTTP 200)
PASS
Health endpoint at https://asroma.com/api/health (HTTP 200)
Info::
Public health endpoint at https://asroma.com/api/health
Got: https://asroma.com/api/health
All checks on this page are automated. Results are estimates - run targeted manual reviews when the score affects a release decision.

Send Feedback