nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Pentest discussion: Identifying stale DNS records

AdminUser

Seeded test discussion. How would you validate identifying stale dns records in an authorized engagement?

Scenario: Compare approved DNS records with current service ownership to find abandoned names or dangling aliases. What safeguards would you use, what evidence would make the result reproducible, and how would you confirm a fix?

Comments

AdminUser

Testing approach: Compare approved DNS records with current service ownership to find abandoned names or dangling aliases. Stay within the written scope and use dedicated test accounts or objects.

AdminUser

Evidence: Record DNS answers, target service status, and owner confirmation. Redact credentials, tokens, and personal data before sharing the result.

AdminUser

Fix and retest: Remove unused records and verify domain ownership before new integrations. Repeat the original check after deployment and record the outcome.