Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.
| Website over IPv6 sacredmedia.social has no AAAA record. | no |
| www over IPv6 www.sacredmedia.social has no AAAA record. | no |
| Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has no AAAA record. | no |
| Nameservers have IPv6 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns1bqx.name.com ✓ns2cqs.name.com ✓ns3jwx.name.com ✓ns4ghm.name.com ✓ | yes |
sacredmedia.social IPv4 only
| A (IPv4) | 13.248.241.119 3.33.148.61 13.248.144.105 35.71.131.46 |
|---|---|
| AAAA (IPv6) | none |
www.sacredmedia.social IPv4 only
| Alias of | floating-soursop-cqlqli7r8j1m8yniw4b74adk.herokudns.com |
|---|---|
| A (IPv4) | 3.33.148.61 13.248.144.105 13.248.241.119 35.71.131.46 |
| AAAA (IPv6) | none |
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
Permanent link: aaaa.bot/r/q1LTtJMQHk · How we measure
Checked 2026-11-12 17:52:15 UTC. Full DNS report: dns.pizza/domain/sacredmedia.social · Age, certificate and blocklists: how.is/sacredmedia.social · JSON: /api/v1/sacredmedia.social