Results for “dns-hijacking”

Deploys DNS, HTTP, and AWS API key canary tokens across network infrastructure to detect unauthorized access and lateral movement, with webhook alerting to Slack, Teams, email, or generic HTTP endpoints.

Resolve hostnames to IP addresses using the `dig` command from bind-utils, including A, AAAA, ANY, and reverse lookups.

Analyze network traffic, logs, and data flows to detect potential data exfiltration via DNS tunneling, cloud storage uploads, encrypted channels, and other indicators of compromise.

Configures and troubleshoots network infrastructure: DNS records, reverse proxies, SSL certificates, firewalls, CDNs, and load balancers.

Deploys canary tokens and honeytokens (fake AWS credentials, DNS canaries, document beacons, database records) that trigger alerts when accessed by attackers. Uses the Canarytokens API and custom webhook integrations for breach detection.

Runs DNS, email security, SSL, WHOIS, and network checks by calling the dnsrobot.net API, with no API key required.

Look up DNS records for any domain, including A, AAAA, MX, NS, TXT, CNAME, and SOA records, with support for multiple domains and JSON output.

Sets up DNS records, SSL/TLS certificates, subdomains, email authentication, and health-check failover routing for Route53, Cloudflare, or GCP Cloud DNS, with optional Terraform output.

Designs and implements CDN architectures, optimizing cache strategies, edge computing, and security for global content delivery.

Deploy a production self-hosted n8n instance on a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS.

Deploy and manage network honeypots using OpenCanary, T-Pot, or Cowrie to detect unauthorized access, lateral movement, and attacker reconnaissance.