No — exchange.contextweb.com is IPv4 only.

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

This is a saved measurement from 2026-11-01 05:47 UTC. Check exchange.contextweb.com live now

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
exchange.contextweb.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
8 of 8 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns01.ppointdns.com ✓ns02.ppointdns.com ✓ns03.ppointdns.com ✓ns04.ppointdns.com ✓dns1.p02.nsone.net ✓dns2.p02.nsone.net ✓dns3.p02.nsone.net ✓dns4.p02.nsone.net ✓
yes

What's keeping exchange.contextweb.com from an A

  1. exchange.contextweb.com is an alias of ma2-secingress-bgp.pulsepoint.com, which has no IPv6
    exchange.contextweb.com is a CNAME, so it can't also have its own AAAA record. Ask whoever runs ma2-secingress-bgp.pulsepoint.com 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

exchange.contextweb.com  IPv4 only

Alias ofexchange.pulsepoint.com → portal.pulsepoint.com → ma2-secingress-bgp.pulsepoint.com
A (IPv4)74.214.194.146
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/gl2Zkqe7Jy · How we measure

Checked 2026-11-01 05:47:32 UTC. Full DNS report: dns.pizza/domain/exchange.contextweb.com · JSON: /api/v1/exchange.contextweb.com