No — app.bible.com is IPv4 only.

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

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
app.bible.com 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 8 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns02.whoeverfindsgodfinds.life ✗dns3.p01.nsone.net ✓ns03.whoeverfindsgodfinds.life ✗ns04.whoeverfindsgodfinds.life ✗ns01.whoeverfindsgodfinds.life ✗dns2.p01.nsone.net ✓dns4.p01.nsone.net ✓dns1.p01.nsone.net ✓
yes
 Which outside scripts, fonts, payments or chat app.bible.com loads from have no IPv6.

What's keeping app.bible.com from an A

  1. app.bible.com is an alias of custom.bnc.lt, which has no IPv6
    app.bible.com is a CNAME, so it can't also have its own AAAA record. Ask whoever runs custom.bnc.lt to enable IPv6 there — or replace the alias with the A and AAAA records they give you. Why some hosts don't offer IPv6
  2. Mail servers without IPv6
    Your domain's mail goes to its own address, which has no AAAA record.

Check again

app.bible.com  IPv4 only

Alias ofcustom.bnc.lt
A (IPv4)44.252.253.233
44.230.115.150
35.167.216.18
AAAA (IPv6)none

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

Copy the evidence — a citation-ready record of this measurement

 Permanent link: aaaa.bot/r/pO5YaqotaN · How we measure

Checked 2026-11-15 17:12:35 UTC. Full DNS report: dns.pizza/domain/app.bible.com · Age, certificate and blocklists: how.is/app.bible.com · JSON: /api/v1/app.bible.com