Skip to content
NewVerdictIQ Connector is here. One Docker image enriches your DNS logs with verdicts inside your network and forwards them to your SIEM.Install guide

Self-Managed Name Server Detected

It indicates that the domain operates using its own name server infrastructure rather than a reputable third-party DNS provider. While legitimate organizations may self-host DNS for flexibility, threat actors often use this approach to maintain full control, obscure DNS changes, and avoid detection mechanisms.

Also surfaces as:
Newly Activated Self-Managed NS
Analyst Q&A

What this signal answers

The questions every analyst asks before acting on this signal.

What it detects01

What does 'Self-Managed Name Server Detected' mean?

It indicates that the domain operates using its own name server infrastructure rather than a reputable third-party DNS provider. While legitimate organizations may self-host DNS for flexibility, threat actors often use this approach to maintain full control, obscure DNS changes, and avoid detection mechanisms.

Why it matters02

Why is self-managed NS considered a malicious indicator?

Because attackers can rapidly update DNS records, re-route traffic, or hide their infrastructure using self-controlled name servers. This behavior is common in phishing, command-and-control (C2), and malware delivery domains that require stealth and agility.

How analysts use it03

Why does 'Newly Activated Self-Managed NS' increase suspicion?

Recently created or switched self-managed NS infrastructure often signals preparation for a malicious campaign. Threat actors frequently deploy new NS configurations just before activating phishing or C2 operations to evade prior detection or blocklisting history.

Evidence shape

What Self-Managed Name Server Detected looks like in the response

A realistic shape of the entry the engine appends to the risk_signals array when this signal fires. Evidence keys are subgroup-default; per-signal overrides documented in the API reference.

json
{
  "slug": "own_ns_usage",
  "name": "Self-Managed Name Server Detected",
  "group": "dns_history",
  "subgroup": "dns_records_mx_ns",
  "direction": "safe",
  "evidence": {
    "ns_provider": "cloudflare.com",
    "ns_provider_tier": "paid_public",
    "ns_stability_days": 412,
    "mx_provider": "google.com",
    "mx_provider_tier": "paid_mail"
  }
}
See in API reference
Siblings

Peers in DNS Records (MX/NS)

12 other signals share the same subgroup. They detect related behaviors and often co-fire on the same IOC.

Self-Managed Mail Infrastructure Detected

It means the domain operates its own mail exchange (MX) servers instead of relying on trusted third-party providers like…

SafeCore
Newly Self-Managed NS Server

The domain has recently configured its own nameservers within a short time window.

Malicious
Double-Flux Behavior Detected

It indicates that both IP and NS (nameserver) records of a domain are changing frequently, a behavior known as 'Double-F…

MaliciousCore
Mail-Flux Behavior Detected

It indicates that the domain frequently changes its MX (Mail Exchange) records. Such behavior is often associated with s…

Malicious
Show 8 more in DNS Records (MX/NS)

Start free, in five minutes

1,000 verdicts/month on the free tier, LLM layer included. No card required.