No — payments.creditcard is IPv4 only.

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

Measured 2026-11-06 01:23 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check payments.creditcard now

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
payments.creditcard has no AAAA record.		no
www over IPv6
www.payments.creditcard has no AAAA record.		no
Mail servers (MX) have IPv6
Null MX — this domain says it doesn't receive mail.		n/a
Nameservers have IPv6
2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns1.afternic.com ✓ns2.afternic.com ✓
yes

First measured 2026-11-06; last confirmed 2026-11-06.

 Which outside scripts, fonts, payments or chat payments.creditcard loads from have no IPv6.

What's keeping payments.creditcard from an A

  1. Give payments.creditcard and www.payments.creditcard 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

Check again

payments.creditcard  IPv4 only

A (IPv4)76.223.54.146
13.248.169.48
AAAA (IPv6)none

www.payments.creditcard  IPv4 only

A (IPv4)76.223.54.146
13.248.169.48
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/u1IHkuxAmZ · How we measure

Checked 2026-11-06 01:23:46 UTC. Full DNS report: dns.pizza/domain/payments.creditcard · Age, certificate and blocklists: how.is/payments.creditcard · JSON: /api/v1/payments.creditcard