Yes — kmf.contact has IPv6.

Has both IPv4 (A) and IPv6 (AAAA) addresses.

IPv6 readiness

Works over IPv6, with one gap: its mail servers lack IPv6.

Website over IPv6 kmf.contact has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3034::6815:4ea7 answers · 443✓ 2606:4700:3035::ac43:8802 answers · 443	yes
www over IPv6 www.kmf.contact has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3035::ac43:8802 answers · 443✓ 2606:4700:3034::6815:4ea7 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. inbound-smtp.us-east-2.amazonaws.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. jonah.ns.cloudflare.com ✓opal.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate: HTTP 200.

https://kmf.contact/ via 2606:4700:3034::6815:4ea7 → 200

works

What's keeping kmf.contact from an A

Mail servers without IPv6
inbound-smtp.us-east-2.amazonaws.com 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.

Check again

kmf.contact Has IPv6

A (IPv4)	172.67.136.2 104.21.78.167
AAAA (IPv6)	2606:4700:3034::6815:4ea7 2606:4700:3035::ac43:8802

www.kmf.contact Has IPv6

Alias of	business-growth.mjegulla.app
A (IPv4)	104.21.78.167 172.67.136.2
AAAA (IPv6)	2606:4700:3035::ac43:8802 2606:4700:3034::6815:4ea7

Browsers on dual-stack networks will usually pick IPv6 here (the "Happy Eyeballs" algorithm races both and prefers v6).

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

IPv6 measurement: kmf.contact
Measured 2026-11-09 15:22:17 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    172.67.136.2, 104.21.78.167
AAAA (IPv6): 2606:4700:3034::6815:4ea7, 2606:4700:3035::ac43:8802
www AAAA:    2606:4700:3035::ac43:8802, 2606:4700:3034::6815:4ea7

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: kmf.contact has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3034::6815:4ea7: answers (TCP 443)
    2606:4700:3035::ac43:8802: answers (TCP 443)
- www over IPv6: www.kmf.contact has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3035::ac43:8802: answers (TCP 443)
    2606:4700:3034::6815:4ea7: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers has an AAAA record.
- Nameservers have IPv6: 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): Loads over IPv6 with a valid certificate: HTTP 200.
    https://kmf.contact/ via 2606:4700:3034::6815:4ea7 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/s1wR8HEXUx

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

Checked 2026-11-09 15:22:17 UTC. Full DNS report: dns.pizza/domain/kmf.contact · Age, certificate and blocklists: how.is/kmf.contact · JSON: /api/v1/kmf.contact