Display more DNSSEC status details
Repository details (node-dnssec-name-shame)
- Project page
- node-dnssec-name-shame
- Project log category
- node-dnssec-name-shame (157 entries)
- Repository
- @joelpurra/node-dnssec-name-shame
- Owner
- @joelpurra
- Issues
- Issues on Github
- Contributors
- Contributors on Github
- Project status
- ⏲️ This project has had recent commits.
- 📂 This project is open.
- 🌠 This project is popular.
- Repository activity period
- 🗓—
- Commits
- 154 commits
- Stars
- 15 stars
Commit details (056a6c8b)
- Author
- Joel Purra
- Authored at
- Committer
- Joel Purra
- Committed at
Commit message
Display more DNSSEC status details
- Make multiple requests for A, AAAA, CNAME, MX and SOA record types.
- Missing records are ignored. If all replies are secure, then the result will be shown as secure.
- Per-record type results are presented separately, if details are expanded by the user.
- CNAME records are followed by getdns (
GETDNS_REDIRECTS_FOLLOW), potentially affecting all record types (right?).- MX records are not followed.
- Didn't yet fix the GUI for lookups without any (matching) records, which also means non-existing domains look weird.
- Fixes #2 – see also details in the issue: https://github.com/joelpurra/node-dnssec-name-shame/issues/2
Raw text
Display more DNSSEC status details - Make multiple requests for A, AAAA, CNAME, MX and SOA record types. - Missing records are ignored. If all replies are secure, then the result will be shown as secure. - Per-record type results are presented separately, if details are expanded by the user. - CNAME records are followed by getdns (`GETDNS_REDIRECTS_FOLLOW`), potentially affecting all record types (right?). - MX records are not followed. - Didn't yet fix the GUI for lookups without any (matching) records, which also means non-existing domains look weird. - Fixes #2 -- see also details in the issue: https://github.com/joelpurra/node-dnssec-name-shame/issues/2