Measurement estimates from a single vantage point — not a compliance certification. Guidance below is for operators, not an SLA.
DNS
Dual-stack
[6] 6/6/6 [O]
Meaning: Shows how many authoritative name servers exist, and how many IPv6 endpoints are configured, responsive, and operational.
IPv4 6/6/6 · IPv6 6/6/6 · location O
| Host | IPv4 | IPv6 | Probes |
|---|
a1-232.akam.net [O] |
193.108.91.232 |
2600:1401:2::e8 |
ipv4 193.108.91.232 ok; ipv6 2600:1401:2::e8 ok; |
a8-65.akam.net [O] |
2.16.40.65 |
2600:1403:a::41 |
ipv4 2.16.40.65 ok; ipv6 2600:1403:a::41 ok; |
a7-64.akam.net [O] |
23.61.199.64 |
2600:1406:32::40 |
ipv4 23.61.199.64 ok; ipv6 2600:1406:32::40 ok; |
a22-66.akam.net [O] |
23.211.61.66 |
2600:1480:7800::42 |
ipv4 23.211.61.66 ok; ipv6 2600:1480:7800::42 ok; |
a5-65.akam.net [O] |
95.100.168.65 |
2600:1480:b000::41 |
ipv4 95.100.168.65 ok; ipv6 2600:1480:b000::41 ok; |
a10-64.akam.net [O] |
96.7.50.64 |
2600:1480:d000::40 |
ipv4 96.7.50.64 ok; ipv6 2600:1480:d000::40 ok; |
Mail
IPv4-only
[2 MX] v4 smtp 4/4/4 v6 smtp 0/0/0 [O]
Meaning: Shows MX footprint and SMTP health per IP family. Operational means an SMTP banner and EHLO exchange succeeded on port 25.
IPv4 SMTP 4/4/4 · IPv6 0/0/0 · location O
| Host | IPv4 | IPv6 | Probes |
|---|
cluster8.us.messagelabs.com [O] |
67.219.247.197, 67.219.246.218, 67.219.250.214 |
— |
ipv4 67.219.247.197 ok; ipv4 67.219.246.218 ok; ipv4 67.219.250.214 ok; |
cluster8a.us.messagelabs.com [O] |
34.75.172.113 |
— |
ipv4 34.75.172.113 ok; |
📌 Action item(s):
- Publish AAAA records for mail (MX): cluster8.us.messagelabs.com, cluster8a.us.messagelabs.com.
Web
Dual-stack
[1] 2/2/2 [O]
Meaning: Shows IPv6 web endpoint readiness for the discovered HTTPS host. Operational means family-specific HTTPS requests complete successfully.
IPv4 2/2/2 · IPv6 2/2/2 · location O
| Host | IPv4 | IPv6 | Probes |
|---|
www.banreservas.com [O] |
23.214.22.147, 23.214.22.143 |
2600:1405:1000:6::17d6:1667, 2600:1405:1000:6::17d6:166d |
ipv4 ok; ipv6 ok; |
DNSSEC
Unsigned
U/-/-
Meaning: Shows whether DNSKEY data is observed at the apex (signed), absent (unsigned), or unavailable due to lookup error.
Apex DNSKEY presence only — not full chain validation.
Analyze on DNSViz
📌 Action item(s):
- Enable DNSSEC signing and publish a DNSKEY at the apex. Use DNSViz to validate the full chain.
DMARC
p=reject, sp=none
p=reject, sp=none — published organizational policy. Strongest published policy (SPF/DKIM alignment still not measured here).
Meaning: Published DMARC policy at _dmarc.banreservas.com.do (DNS TXT). Shows organizational policy (p=) and subdomain policy (sp=) when set.
Record at _dmarc.banreservas.com.do:
v=DMARC1;p=reject;sp=none;pct=100;fo=1;ri=86400;rua=mailto:dmarc_agg@vali.email,mailto:banreservas.com.do@danaconnect-dmarc.com;ruf=mailto:dmrcrptsu@banreservas.com,mailto:banreservas.com.do@danaconnect-dmarc.com;rf=afrf
Policy publication only — SPF/DKIM not measured. Not part of the 0–4 row score.
Check on dmarcian