No — securecap.cat is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

Measured 2026-10-31 06:28 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check securecap.cat now

First measured 2026-10-30; last confirmed 2026-10-31.

What's keeping securecap.cat from an A

1. Give securecap.cat and www.securecap.cat an IPv6 address
   Ask your hosting provider for the site's IPv6 address (or the hostname to point at), then publish it as an AAAA record. If your host doesn't offer IPv6, a proxy that does can sit in front. How to add an AAAA record
2. Mail servers without IPv6
   mail.securecap.cat has no AAAA record, so mail from IPv6-only servers can't reach it directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.
3. Nameservers without IPv6
   ns3.dinahosting.com, ns2.dinahosting.com, ns4.dinahosting.com, ns.dinahosting.com all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

What this means

Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it

Checked 2026-10-31 06:28:38 UTC. Full DNS report: dns.pizza/domain/securecap.cat · JSON: /api/v1/securecap.cat