Results for “dnscat2”

Manage Azure Data Lake Storage Gen2 with Python SDK for hierarchical file systems, big data analytics, and file/directory operations.

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

Detect network reconnaissance and port scanning using Suricata and Snort IDS signatures, threshold-based detection rules, and traffic anomaly analysis to identify Nmap, Masscan, and custom scanning activity.

Manages NS1 DNS zones, records, filter chains, monitoring jobs, and traffic steering via the NS1 API, with a discovery-first workflow for inspection and troubleshooting.

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

Register on-chain agent identities, publish content, message other agents, hire specialists, post bounties, and earn NOOK rewards on Base Mainnet.

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.

Deploy web applications, APIs, and background services on AWS using CDK, covering EC2, ECS Fargate, Lambda, API Gateway, CloudFront, Route 53, RDS, ElastiCache, IAM, and monitoring.

AWS SDK integration for Node.js (v3) and Python (boto3). Core services: S3, Lambda, DynamoDB, SQS, SNS, CloudWatch, IAM. Configuration, credentials, and production patterns. USE WHEN: user mentions "AWS", "Amazon Web Services", "Lambda", "DynamoDB", "SQS", "SNS", "CloudWatch", "IAM", "boto3", "aws-sdk" DO NOT USE FOR: S3 file operations - use `cloud-storage`; SQS messaging patterns - use `sqs`; Azure/GCP - use respective skills

NATS cloud-native messaging system. Covers Core NATS, JetStream persistence, and request/reply patterns. Use for lightweight, high-performance microservices communication. USE WHEN: user mentions "nats", "jetstream", "cloud-native messaging", "request/reply", "subject wildcards", asks about "lightweight messaging", "microservices communication", "nats streaming" DO NOT USE FOR: complex routing - use `rabbitmq`; AWS-native - use `sqs`; Azure-native - use `azure-service-bus`; JMS compliance - use `activemq`; persistent queues only - use dedicated broker