Skip to main content

DNS & Email Security Report for globalcyberalliance.org

An automated analysis of globalcyberalliance.org's DNS configuration, email authentication (SPF, DKIM, DMARC), DNSSEC chain, IPv6 readiness, and transport security, based on a scan made on November 9, 2026.

B89/100
Good

Good security, minor improvements possible

Overall security score: 89/100 · Grade B (Good) · 44 checks passed, 9 failed, 8 not assessed

Key findings for globalcyberalliance.org

SPF
globalcyberalliance.org publishes an SPF record that ends in -all, so receivers are told to reject mail from servers it does not list.v=spf1 include:_spf.mlsend.com include:_spf.google.com -all
DMARC
The DMARC policy tells receivers to reject mail that fails authentication, and aggregate reports are requested via rua.v=DMARC1; p=reject; fo=1; rua=mailto:3941b663@inbox.ondmarc.com,mailto:2zw1qguv@ag.dmarcian.com,mailto:dmarc_agg@vali.email; ruf=mailto:2zw1qguv@fr.dmarcian.com,mailto:gca-ny-sc@globalcyberalliance.org;
DKIM
A DKIM public key was found at the selector "k1".
MTA-STS
No MTA-STS policy is published, so inbound mail can fall back to unencrypted delivery.
DNSSEC
The zone is DNSSEC-signed and validates from the root down.
CAA
10 CAA records restrict which certificate authorities may issue certificates for globalcyberalliance.org.
IPv6
5 of 5 mail servers can be reached over IPv6.
HTTPS
HTTP redirects to HTTPS, and HSTS is set with max-age=15552000.

How globalcyberalliance.org compares

With 89/100, globalcyberalliance.org scores higher than 120 of the 133 other domains in the IntoDNS.ai report set (median score 71/100, all scanned in the same run). Within its sector, CERTs, standards bodies and directories, it ranks 3 of 12.

Similar domains

All domain security reports

This report is a stored snapshot

This page shows a snapshot from November 9, 2026. DNS changes frequently — for live records, propagation, and deep checks, run a fresh interactive scan of globalcyberalliance.org at /scan.

Run a fresh live scan

Detailed check results

DNS

100%pass
  • A record presentcritical

    3 A record(s) found

  • AAAA record presentrecommended

    3 AAAA record(s) found

  • MX records presentrecommended

    5 MX record(s) found

  • NS records presentcritical

    2 NS record(s) found

  • SOA record presentcritical

    SOA record found

  • Multiple nameserversrecommended

    2 nameservers configured ✓

  • SOA serial formatinfo

    Serial 2419148361 (valid, managed DNS format)

  • SOA timers validinfo

    Refresh: 10000s ✓, Retry: 2400s ✓, Expire: 604800s ✓

  • No lame nameserversinfo

    2 NS all responding ✓

  • Glue records presentinfo

    No glue needed

  • WWW record configuredinfo

    A record matches apex

  • MX servers have PTR recordsrecommended

    10 MX IPs all have PTR records ✓

  • MX servers have FCrDNSrecommended

    10 MX IPs have forward-confirmed reverse DNS ✓

DNSSEC

100%pass
  • DNSSEC signedrecommended

    DNSSEC is enabled ✓

  • DNSSEC validation OKcritical

    DNSSEC validates correctly ✓

  • NSEC3 RFC 9276 compliantrecommended

    Not applicable (domain uses NSEC or is not DNSSEC-signed)

  • RRSIG signatures validrecommended

    RRSIG signature expires in 1 days — renewal needed

  • Modern DNSSEC algorithmoptional

    ECDSA P-256 (algorithm 13) — modern ✓

  • DS digest algorithm modernrecommended

    DS digest: SHA-256 — modern ✓

  • DNSKEY algorithm secureoptional

    DNSKEY: ECDSA P-256 — modern ✓

  • RRSIG TTL saferecommended

    Record TTLs do not exceed RRSIG validity periods ✓

  • Chain of trust completecritical

    Cryptographic chain validated to the root trust anchor with local BIND delv ✓

IPv6

100%pass
  • Website reachable via IPv6recommended

    3 AAAA record(s) ✓

  • Mail servers publish IPv6recommended

    5/5 MX server(s) publish IPv6 ✓

  • Nameservers reachable via IPv6recommended

    2/2 NS server(s) with IPv6 ✓

Email security

81%pass
  • SPF record presentcritical

    v=spf1 include:_spf.mlsend.com include:_spf.google.com -all

  • SPF syntax validcritical

    SPF syntax is correct ✓

  • SPF policy strict (-all)recommended

    SPF uses -all (hard fail) ✓

  • DKIM foundrecommended

    DKIM selector: k1 ✓

  • DMARC record presentrecommended

    v=DMARC1; p=reject; fo=1; rua=mailto:3941b663@inbox.ondmarc.com,mailto:2zw1qguv@ag.dmarcian.com,mailto:dmarc_agg@vali.email; ruf=mailto:2zw1qguv@fr.dmarcian.com,mailto:gca-ny-sc@globalcyberalliance.org;

  • DMARC policy quarantine or betterrecommended

    DMARC policy: reject ✓

  • DMARC policy rejectoptional

    DMARC policy: reject ✓

  • BIMI record presentoptional

    BIMI logo: https://bimi.entrust.net/globalcyberalliance.org/logo.svg

  • BIMI configuration validoptional

    BIMI correctly configured ✓

  • MTA-STS record presentoptional

    MTA-STS configured ✓

  • MTA-STS policy enforcedoptional

    MTA-STS not configured

  • MX records validcritical

    5 MX record(s) ✓

  • MX domains use DNSSECrecommended

    0/1 MX domain(s) have DNSSEC. Ask your mail provider to enable DNSSEC

  • MX DNSSEC validation OKrecommended

    DNSSEC not enabled for MX domains

  • Mail servers not blacklistedinfo

    Not listed on 11 blacklists, but Spamhaus SBL could not be checked from IntoDNS.ai — result inconclusive

  • No critical blacklist listingsinfo

    Not listed on 11 blacklists, but Spamhaus SBL could not be checked from IntoDNS.ai — result inconclusive

Web security

72%warning
  • CAA records presentrecommended

    10 CAA record(s) ✓

  • CAA policy strictoptional

    CAA limits certificate authorities ✓

  • TLSA records (DANE)optional

    No TLSA/DANE records. Add TLSA at _25._tcp.mail for DANE email encryption

  • DANE configuration validoptional

    No DANE configured

  • No sensitive info in TXTcritical

    No sensitive data leaked ✓

  • Verification records reviewedinfo

    3 verification record(s): Microsoft 365, Google, Apple. Consider if all are still needed

  • HTTPS availablecritical

    HTTPS working (status 200) ✓

  • Valid certificatecritical

    Certificate chain is valid and trusted ✓

  • HTTP redirects to HTTPScritical

    HTTP automatically redirects to HTTPS ✓

  • HSTS enabledrecommended

    HSTS enabled (max-age=15552000, includeSubDomains, preload) ✓

  • HSTS max-age >= 1 yearoptional

    max-age=15552000 is too short. Set to 31536000 (1 year) or higher

  • X-Frame-Options headerrecommended

    X-Frame-Options: SAMEORIGIN ✓

  • X-Content-Type-Options headerrecommended

    X-Content-Type-Options: nosniff ✓

  • Content-Security-Policy headerrecommended

    Content-Security-Policy configured without critical weaknesses ✓

  • Referrer-Policy headerrecommended

    No Referrer-Policy header. Add Referrer-Policy: strict-origin-when-cross-origin

  • security.txt presentoptional

    No security.txt. Create /.well-known/security.txt with Contact and Expires fields (RFC 9116)

  • security.txt validoptional

    No security.txt configured

  • HTTP/3 (QUIC) supportedoptional

    HTTP/3 (QUIC v1) on port 443 Detection methods: QUIC probe: inconclusive (no reply — trigger may be dropped or UDP/443 filtered) Alt-Svc header: h3=":443" Cache: 24h (ma=86400) HTTPS DNS record: alpn="h3, h2" Encrypted Client Hello (ECH): supported

  • QUIC UDP reachableinfo

    QUIC probe inconclusive (no reply — trigger may be dropped or UDP/443 filtered). Not a negative signal; h3 is judged from Alt-Svc / HTTPS record

  • HTTPS DNS record (SVCB)optional

    HTTPS record advertises h3, h2 ✓ + ECH

About this report

IntoDNS.AI evaluates globalcyberalliance.org against DNS hygiene, email authentication, and transport-security best practices, scoring each check and rolling them up into an overall grade. This is a stored snapshot of public DNS as observed on November 9, 2026; it may differ from a live scan if the domain has since changed its configuration.

Want to check your own domain? Scan any domain on the homepage.

Snapshot from: November 9, 2026 · Google Public DNS