Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.
| Website over IPv6 fetchdeliveryservices.com has no AAAA record. | no |
| www over IPv6 www.fetchdeliveryservices.com has no AAAA record. | no |
| Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. fwd1.porkbun.com ✗fwd2.porkbun.com ✗ | no |
| Nameservers have IPv6 4 of 4 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. curitiba.ns.porkbun.com ✓fortaleza.ns.porkbun.com ✓maceio.ns.porkbun.com ✓salvador.ns.porkbun.com ✓ | yes |
fetchdeliveryservices.com IPv4 only
| A (IPv4) | 104.16.36.105 104.16.42.105 104.19.240.93 104.19.241.93 |
|---|---|
| AAAA (IPv6) | none |
www.fetchdeliveryservices.com IPv4 only
| Alias of | app.bubble.io |
|---|---|
| A (IPv4) | 104.17.124.183 104.17.123.183 |
| 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/PtMy1BC5DA · How we measure
Checked 2026-11-06 19:20:05 UTC. Full DNS report: dns.pizza/domain/fetchdeliveryservices.com · Age, certificate and blocklists: how.is/fetchdeliveryservices.com · JSON: /api/v1/fetchdeliveryservices.com