List your agent

BlackVeil DNS & Email Security Scanner

MCP server● Hosted · onlinev3.117.3

DNS and email security scanner with 82 MCP tools for SPF, DMARC, DNSSEC, SSL, and brand audits

What you can do with it

Share of each task's required capabilities it covers

Prefer a ready-made agent?

An MCP server is a connector for your own assistant. These finished products do the job for you: scan code for vulnerabilities.
All AI agents to scan code for vulnerabilities, ranked →

Similar tools

Listed for the same task: scan code for vulnerabilities

Reviews

No review yet. Used BlackVeil DNS & Email Security Scanner? Be the first to help others choose.

What it does

BlackVeil DNS & Email Security Scanner is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: security scanning. That makes it a candidate for tasks such as scan code for vulnerabilities or review pull requests.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version3.117.3
PriceNot in the registry
First seen26 Sept 2026
Last checked7h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1d ago (live check)

Hosted endpoint

  • https://dns-mcp.blackveilsecurity.com/mcp streamable-http

In Claude Code: claude mcp add --transport http blackveil-dns-email-security-scanner https://dns-mcp.blackveilsecurity.com/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "blackveil-dns-email-security-scanner": {
      "url": "https://dns-mcp.blackveilsecurity.com/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1d ago

ONLINE BlackVeil DNS & Email Security Scanner answered an MCP connection on 16 Nov 2026 and introduced itself as Blackveil DNS 3.116.0 (MCP protocol 2025-06-18).

82 tools offered to AI assistants

  • get_access_context · Read the effective authentication context for this request: tier, owner-IP-gate disposition, a keyed pseudonymous principal reference, server version and observation time. Performs no target checks or quota/session/cache/job writes. An unav
  • check_mx · Look up MX records for a domain. Identifies which mail servers receive inbound email for the domain and which email hosting provider is used (Google Workspace, Microsoft 365, Proofpoint, etc.). Use when asked which email provider hosts inbo
  • check_spf · Look up and validate the SPF record for a domain. Lists all IP addresses and third-party senders authorised to send email on behalf of the domain, flags syntax errors, and shows the trust surface (which mail servers are whitelisted). Use wh
  • check_dmarc · Look up and validate a domain's DMARC record: enforcement level (none/quarantine/reject), alignment mode, and aggregate/forensic reporting destinations. Use to find a domain's DMARC enforcement, whether it sends aggregate reports, or whethe
  • check_dkim · Look up DKIM records for a domain. Probes common selectors, validates the signing algorithm used for outgoing email (RSA-1024/2048, Ed25519), and reports key strength. Use to verify that outbound email signatures are cryptographically sound
  • check_dnssec · Check DNSSEC status for a domain. Verifies whether DNS is tamper-proof and protected against cache poisoning and DNS spoofing attacks by validating DNSKEY and DS records. Reports whether DNSSEC is enabled and validating. Part of the scan_do
  • check_ssl · Check HTTPS/TLS posture: reachability, HSTS, HTTP-to-HTTPS redirect, and certificate issuer, expiry, days remaining and SAN count from public CT logs (the latest LOGGED certificate, which may differ from the one served). TLS protocol versio
  • check_mta_sts · Check whether a domain enforces SMTP TLS for inbound mail via MTA-STS, protecting against downgrade attacks. Queries _mta-sts.<domain> and fetches the policy file, reports mode (enforce/testing/none) and MX coverage. Use to verify whether i
  • check_ns · Audit a domain’s nameserver delegation and redundancy. Identifies the DNS hosting provider and, when the infrastructure probe is available, directly compares parent and child NS sets, verifies authoritative AA responses, and checks required
  • check_caa · Look up CAA records for a domain. Shows which Certificate Authorities are authorized to issue certificates. Part of the scan_domain audit.
  • check_bimi · Check the BIMI record at default._bimi.<domain>: validates the logo URL (l=), the presence of mark-certificate authority evidence (a=; a bare URL, so VMC vs CMC is not determined), and the DMARC enforcement prerequisite (p=quarantine/reject
  • check_tlsrpt · Check whether a domain has SMTP TLS Reporting (TLS-RPT) configured. Queries _smtp._tls.<domain> for the v=TLSRPTv1 record and validates its reporting destination (rua= mailto:/https:), flagging a missing record, duplicate records, or an inv
Show 70 more
  • check_http_security · Audit browser-facing HTTP security headers over HTTPS: Content-Security-Policy (unsafe-inline/unsafe-eval/wildcards), X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy and COOP/COEP/CORP; also detects CDN/WAF inte
  • check_dane · Check DANE/TLSA pinning for SMTP: looks up TLSA records at _25._tcp.<mx-host> for each MX and validates their fields and DNSSEC backing. Records are reported present but UNVERIFIED: there is no port-25 certificate probe, so a pin is never c
  • check_ptr · Verify forward-confirmed reverse DNS (PTR/FCrDNS) for mail servers. Part of the scan_domain audit.
  • check_dane_https · Verify DANE/TLSA pinning for HTTPS (port 443): looks up TLSA records at _443._tcp.<domain> and validates fields and DNSSEC backing. Reported present but UNVERIFIED in every deployment: comparison with the served certificate is withdrawn (th
  • check_svcb_https · Validate HTTPS/SVCB records (RFC 9460) for modern transport capability advertisement. Part of the scan_domain audit.
  • check_lookalikes · Detect active typosquat and lookalike/homoglyph domains that impersonate your brand and could be used in phishing. Identifies character-substitution and visual-confusion domains registered by attackers. Distinct from check_shadow_domains (T
  • check_subdomailing · Detect SubdoMailing risk: analyzes the SPF include chain for dangling or hijackable subdomains that could let an attacker send email as the domain. Use when you want to know if an SPF include chain can be hijacked through a dangling domain,
  • scan_domain · Run a full DNS and email security audit for one domain across every scan-included check (SPF, DKIM, DMARC, DNSSEC and more); returns an overall score, NIST-aligned letter grade (A+ to F), maturity stage and prioritized findings. Use for a c
  • batch_scan · Bulk-scan up to 10 domains in parallel with a full security audit each; returns score, NIST-aligned letter grade (A+ to F) and finding counts per domain. Use to audit several domains at once; use compare_domains for a side-by-side compariso
  • batch_scan_start · Start a durable asynchronous scan of 1–10 domains. Returns a stable job ID; replaying the same idempotency key with the same principal, normalized inputs, and scoring versions returns the same job.
  • batch_scan_status · Read the owner-scoped status of an asynchronous batch scan.
  • batch_scan_findings · Fetch owner-scoped findings for a completed asynchronous batch scan.
  • compare_domains · Side-by-side security comparison of 2–5 domains. Shows relative scores, category gaps, and unique weaknesses for each domain. Use when comparing your security posture against a competitor, or doing a head-to-head comparison between multiple
  • compare_baseline · Compare a domain's current security configuration against a fixed policy baseline to determine compliance. Use to check whether a domain meets a policy requirement — not for tracking improvement/regression over time (use analyze_drift) and
  • check_shadow_domains · Find alternate TLD variants of a domain (e.g. example.net, example.co) that have weak or missing email authentication and could be used to spoof email. Use when asked about TLD variants with email auth gaps — distinct from check_lookalikes
  • check_txt_hygiene · Audit TXT records for stale entries and SaaS exposure.
  • check_mx_reputation · Check whether the mail server (MX) IP addresses are listed on spam blocklists (Spamhaus, Barracuda, SORBS, and other RBLs). Also verifies reverse DNS for MX hosts. Use when you want to know if your mail server IP is blacklisted, or if your
  • check_srv · Map a domain's DNS-visible service footprint by probing 19 common SRV prefixes (email, calendar, messaging, directory, web) in parallel; returns discovered services and flags insecure advertisements such as plaintext IMAP/POP3/LDAP with no
  • check_zone_hygiene · Audit DNS zone hygiene: identifies sensitive or forgotten subdomains exposed in DNS, stale SOA records, and zone propagation issues. Use to find any sensitive subdomains that should not be publicly visible, or to audit overall DNS zone clea
  • generate · Generate a DNS/email security remediation artifact. Artifact types: spf_record (build a new SPF record), dmarc_record (create a DMARC policy), dkim_config (DKIM key setup), mta_sts_policy (generate an MTA-STS policy file), fix_plan (priorit
  • get_domain_rank · Rank a domain against its country or global cohort using the GSI benchmark corpus. Accepts a domain score (from scan_domain) and optional country/sector; returns a percentile: "scores better than X% of peers". Owner-gate exempt — public coh
  • get_benchmark · Get industry benchmark data: shows what percentile a domain's security score ranks at within its sector or country cohort, the mean score, and the most common DNS security failures across the industry. Use when asked how a score compares to
  • get_provider_insights · Get security benchmarks and common configuration issues for a specific email or DNS service-provider cohort (e.g. Google Workspace customers, Microsoft 365 customers). Use when asked how an email service provider compares to competitors on
  • assess_spoofability · Compute a composite email spoofability risk score (0-100, higher = more spoofable) from SPF trust surface, DMARC enforcement and DKIM coverage. Returns a risk level (minimal to critical), per-control sub-scores and a plain-language summary.
  • check_resolver_consistency · Check DNS consistency across 4 public resolvers.
  • explain_finding · Explain a finding with impact and remediation.
  • map_supply_chain · Map DNS-visible third-party service dependencies for a domain. Correlates SPF, NS, TXT verifications, SRV services, and CAA records to reveal which third-party vendors can send email as the domain, control DNS, or access integrated services
  • analyze_drift · Measure whether a domain's DNS security posture improved or regressed versus a prior scan snapshot; returns a drift classification (improving/stable/regressing/mixed), score delta, and lists of improvements and regressions. Use for "did our
  • validate_fix · Re-check a specific security control after applying a fix, to confirm the finding is now resolved. Use only when a fix has already been applied and you want to verify or confirm the remediation was successful — not for initial inspection of
  • resolve_spf_chain · Trace the full SPF include chain for a domain. Recursively resolves all includes, shows lookup count, tree depth, and flags circular includes or exceeding the 10-lookup limit.
  • discover_subdomains · Find subdomains via Certificate Transparency logs to reveal shadow IT and forgotten services. Returns a CT SAMPLE, not an asset inventory: counts are a lower bound, hosts without a logged certificate never appear, and a per-source `coverage
  • map_compliance · Map scan findings to compliance frameworks: NIST 800-177, PCI DSS 4.0, SOC 2, CIS Controls. Shows pass/fail/partial status per control.
  • sge_quickscan · Check whether ONE domain meets the New Zealand Secure Government Email (SGE) requirements due October 2026. Reports seven controls (DMARC p=reject, SPF -all, DKIM, SMTP transport TLS, MTA-STS enforce, TLS-RPT, sub-domain coverage) as satisf
  • prioritize_portfolio_leads · Rank a brand’s portfolio (or an explicit domain set) into prioritized registrar-partner sales leads by product-gap value × severity. Multi-domain, paid. Reuses map_registrar_products per domain, then ranks. Distinct from map_registrar_produ
  • simulate_attack_paths · Analyze current DNS posture and enumerate specific attack paths an adversary could exploit, with severity, feasibility, steps, and mitigations.
  • check_dbl · Check domain reputation against DNS-based Domain Block Lists (Spamhaus DBL, URIBL, SURBL). Returns listing status with decoded return codes.
  • check_rbl · Check MX server IP reputation against 6 DNS-based Real-time Blocklists (SpamCop, UCEProtect, Mailspike, Barracuda, PSBL). Resolves MX hosts to IPs first.
  • cymru_asn · Map domain IPs to Autonomous System Numbers via Team Cymru DNS. Returns ASN, prefix, country, registry, and organization for each IP. Flags high-risk hosting ASNs.
  • rdap_lookup · Fetch domain registration data via RDAP (modern WHOIS replacement). Returns the domain registrar (the company the domain was registered with), registrant contact, creation/expiration dates, EPP status codes, and domain age. Use when asked w
  • check_realtime_threat_feed · Check a domain against BlackVeil real-time threat intelligence (curated intel-gateway feed). Distinct from DNSBL checks. Operator-deploy only; degrades to info when unprovisioned.
  • check_nsec_walkability · Assess zone walkability risk by analyzing NSEC3PARAM configuration. Detects plain NSEC zones, weak NSEC3 parameters, and opt-out flags.
  • check_dnssec_chain · Walk the full DNSSEC chain of trust from the DNS root down to the target domain, tracing DS/DNSKEY records and algorithm usage at each zone level. Use when asked to trace the chain of trust from the DNS root, or to see the full DNSSEC deleg
  • check_agent_discovery · Assess IETF BANDAID agent-discovery DNS records: finds SVCB agent records under _agents, reports whether the discovery zone is DNSSEC-anchored (unsigned means spoofable endpoints), evaluates DANE/TLSA binding trust and checks capability-doc
  • check_llms_txt · Inspect a domain's /llms.txt and /llms-full.txt for links and install commands an AI agent could inherit. Sweeps external link hosts for dangling CNAMEs and deprovisioned-service fingerprints (evidence, not proof it is claimable) and checks
  • check_dnskey_strength · Audit DNSKEY signing algorithms used for DNSSEC: reports the algorithm in use (RSA/SHA-1, RSA/SHA-256, ECDSA P-256, Ed25519, etc.) and flags deprecated ones (RSA/SHA-1, DSA), independent of whether the chain validates. Use when asked which
  • check_fast_flux · Detect fast-flux DNS behavior: performs multiple rounds of A/AAAA queries and checks whether IP addresses are rotating rapidly on each DNS query (a sign of botnet or malicious infrastructure). Compares IP answer sets and TTLs across rounds
  • check_subdomain_takeover · Sweep subdomains for dangling CNAMEs pointing at deprovisioned cloud services an attacker could claim (subdomain takeover); detects 16 provider families such as AWS S3/CloudFront, Azure, GCP Storage, Heroku, GitHub Pages, Vercel and Firebas
  • check_authoritative_dns_infra · Measure a hostname's authoritative DNS posture by querying its nameservers directly over TCP/53 from one vantage: reachability, AA flag, recursion exposure, SOA serial consistency, DNSKEY/RRSIG presence (not validation), IPv4/IPv6 parity. A
  • check_root_server_set · Query a rotating sample of 3 root servers per call and compare the priming NS set, glue, SOA serials, and cross-root consistency against the embedded official root hints. Uses BV_INFRA_PROBE when available; without it, returns the embedded
  • discover_brand_domains · Discover all domains that belong to a brand's portfolio by aggregating certificate, DNS, redirect, and mail-policy signals. Use when asked what domains are part of a brand portfolio, or to find all domains related to a brand. Pass the EXACT
  • discover_brand_domains_start · Start an async brand-domain discovery for the EXACT seed domain provided (the async sibling of discover_brand_domains, which can run ~24s and time out interactive clients). Same args as discover_brand_domains. Returns { auditId, queuedAt, e
  • discover_brand_domains_status · Poll the status of an async brand-domain discovery started with discover_brand_domains_start. Returns status (queued | running | completed | failed) and progress. Owner-scoped — operationIds owned by other principals surface as notFound.
  • discover_brand_domains_findings · Fetch the ranked candidate domains (the discovery CheckResult) for an async run started with discover_brand_domains_start. Returns notReady while the discovery is still in-flight; the discovery result once complete. Owner-scoped.
  • brand_audit_single · Run a full brand audit on one target (optional standard/deep depth, brand aliases, candidate domains). Discovers brand-related domains, looks up registrar and registrant, and classifies each as consolidated, shadowIt, authorized vendor, ind
  • brand_audit_batch_start · Enqueue an async brand audit across up to 50 target domains with optional standard/deep discovery depth, brand aliases, and caller-supplied candidate domains. Returns { auditId, queuedAt, targetCount, etaSeconds } immediately; poll with bra
  • brand_audit_status · Poll the status of an enqueued brand audit. Returns audit-level status (queued | running | completed | failed), progress 'N/M', and per-target statuses. Owner-scoped — auditIds owned by other principals surface as notFound.
  • brand_audit_get_report · Fetch the result JSON of a completed brand audit: the per-target CheckResult when `target` is set, else the audit-level aggregate; returns notReady while in flight. When a PDF sidecar exists, metadata includes pdfUrl, an authenticated /repo
  • list_brand_audit_watches · Returns the caller's recurring brand-audit watches: watchId, domain, interval, webhook presence, last-run time, and active state. Owner-scoped. Read-only.
  • register_brand_audit_watch · Creates a recurring brand-audit watch for a domain on a daily/weekly/monthly cadence. Each run enqueues a fresh brand_audit_batch_start and (when a webhook is configured) POSTs a diff webhook on classification drift. Returns the new watchId
  • delete_brand_audit_watch · Permanently removes a recurring brand-audit watch by watchId. Owner-scoped — a watchId owned by another principal surfaces as notFound. Returns confirmation of deletion.
  • scan_buckets_start · Start an async cloud-bucket discovery scan for a target domain. Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. Returns a scanId immediately — poll progress with scan_bu
  • scan_buckets_status · Poll the status of a cloud-bucket discovery scan by scanId. Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. Returns scan status (running | completed | failed) and progre
  • scan_buckets_findings · Retrieve findings from a completed cloud-bucket discovery scan by scanId. Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. The scanId is required so reads can be owner-sc
  • osint_investigate_domain_start · Start an async OSINT investigation for a domain. Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. Returns an investigationId immediately — poll with osint_investigation_s
  • osint_investigate_infrastructure_start · Start an async deep-infrastructure OSINT investigation for a query (domain, IP, or org). Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. Returns an investigationId immed
  • osint_investigate_supply_chain_start · Start an async supply-chain OSINT investigation for a query. Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. Returns an investigationId immediately — poll with osint_inv
  • osint_investigate_username_start · Start an async OSINT investigation for a username (cross-platform presence, breach correlation). Owner/enterprise tier only — people-centric OSINT is restricted to prevent misuse. Returns an investigationId immediately — poll with osint_inv
  • osint_investigate_email_start · Start an async OSINT investigation for an email address (breach exposure, account correlation). Owner/enterprise tier only — people-centric OSINT is restricted to prevent misuse. Returns an investigationId immediately — poll with osint_inve
  • osint_investigation_status · Poll the status of an OSINT investigation by investigationId. Operator-deploy only; targets must be operator-authorized on the recon watchlist; degrades to info when unprovisioned. Returns current status (running | completed | failed) and p
  • osint_investigation_report · Retrieve the final report of a completed OSINT investigation by investigationId. For a deep_infrastructure investigation the report also composes discover_subdomains for the target (a cached CT sample under `ctDiscovery`, never an inventory

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Version3.117.3DECLAREDSRC-001 Official MCP Registry7h ago
Hosted endpointhttps://dns-mcp.blackveilsecurity.com/mcpDECLAREDSRC-001 Official MCP Registry7h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry7h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry7h ago
Websitehttps://www.blackveilsecurity.com/dnsDECLAREDSRC-001 Official MCP Registry7h ago
Repositoryhttps://github.com/MadaBurns/bv-mcpDECLAREDSRC-001 Official MCP Registry7h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry7h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry7h ago

Change history

  • VERSION17 Nov 2026
    3.117.2 → 3.117.3
  • VERSION17 Nov 2026
    3.117.1 → 3.117.2
  • VERSION17 Nov 2026
    3.117.0 → 3.117.1
  • VERSION17 Nov 2026
    3.116.2 → 3.117.0
  • VERSION16 Nov 2026
    3.116.1 → 3.116.2
  • VERSION16 Nov 2026
    3.116.0 → 3.116.1
  • VERSION16 Nov 2026
    3.115.0 → 3.116.0
  • VERSION15 Nov 2026
    3.114.0 → 3.115.0
  • VERSION14 Nov 2026
    3.113.0 → 3.114.0
  • VERSION13 Nov 2026
    3.112.0 → 3.113.0
  • VERSION13 Nov 2026
    3.111.4 → 3.112.0
  • VERSION13 Nov 2026
    3.111.3 → 3.111.4
  • VERSION13 Nov 2026
    3.111.2 → 3.111.3
  • VERSION12 Nov 2026
    3.111.1 → 3.111.2
  • VERSION12 Nov 2026
    3.111.0 → 3.111.1
  • VERSION10 Nov 2026
    3.110.1 → 3.111.0
  • VERSION10 Nov 2026
    3.110.0 → 3.110.1
  • VERSION08 Nov 2026
    3.109.1 → 3.110.0
  • VERSION05 Nov 2026
    3.109.0 → 3.109.1
  • VERSION04 Nov 2026
    3.108.4 → 3.109.0
  • VERSION03 Nov 2026
    3.108.3 → 3.108.4
  • VERSION02 Nov 2026
    3.108.1 → 3.108.3
  • VERSION01 Nov 2026
    3.108.0 → 3.108.1
  • VERSION01 Nov 2026
    3.107.1 → 3.108.0
  • VERSION01 Nov 2026
    3.107.0 → 3.107.1
  • VERSION31 Oct 2026
    3.105.0 → 3.107.0
  • VERSION29 Oct 2026
    3.104.4 → 3.105.0
  • VERSION29 Oct 2026
    3.104.1 → 3.104.4
  • VERSION28 Oct 2026
    3.104.0 → 3.104.1
  • VERSION28 Oct 2026
    3.103.3 → 3.104.0

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

Do you run BlackVeil DNS & Email Security Scanner? Know when it stops answering

For publishers · optional

Its hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.

Monitor BlackVeil DNS & Email Security ScannerLaunch offer $39.99 once, for life instead of $9.99/month · All plans

Monitoring never changes a score or a rank.

Are you the publisher of BlackVeil DNS & Email Security Scanner?

Free · show your listing

An independent listing builds trust with your buyers. Announce it, and add the badge to your website or README.

Announce it on LinkedIn
Listed on Electra IndexListed on Electra Index
<a href="https://electraindex.com/mcp/blackveil-dns-email-security-scanner?utm_source=badge&utm_medium=share&utm_campaign=listing"><img src="https://electraindex.com/api/badge/blackveil-dns-email-security-scanner/card" width="260" height="72" alt="Listed on Electra Index"></a>

Questions about BlackVeil DNS & Email Security Scanner

How do I connect BlackVeil DNS & Email Security Scanner?

Use the hosted endpoint https://dns-mcp.blackveilsecurity.com/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

What tools does BlackVeil DNS & Email Security Scanner offer?

When Electra Index connected on 16 Nov 2026, it listed 82 tools: get_access_context, check_mx, check_spf, check_dmarc, check_dkim, check_dnssec, check_ssl, check_mta_sts and more. The full list is in "Live check" above.

Is BlackVeil DNS & Email Security Scanner online?

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1d ago.

What can I use BlackVeil DNS & Email Security Scanner for?

Based on its description, it is most relevant to: scan code for vulnerabilities, review pull requests.