Commit 3cdbdee621
Verified · cmc
Layout: unified · split
README.md added +56
| @@ -0,0 +1,56 @@ | |||
| 1 | # domain-dig | ||
| 2 | |||
| 3 | Domain Dig is a minimal iOS to perform DNS lookups. | ||
| 4 | |||
| 5 | ## Features | ||
| 6 | |||
| 7 | Data provided by a Domain Dig search: | ||
| 8 | |||
| 9 | - Reachability | ||
| 10 | - Redirect Chain | ||
| 11 | - DNS Records | ||
| 12 | - Email Security | ||
| 13 | - SSL/TLS Certificate | ||
| 14 | - HTTP Headers | ||
| 15 | - "Grade" for header security | ||
| 16 | - IP Location | ||
| 17 | - Open Ports | ||
| 18 | - Custom port checks | ||
| 19 | |||
| 20 | Extra features: | ||
| 21 | |||
| 22 | - Save favorite domains for quick reuse | ||
| 23 | - Check historical log of searches and their results | ||
| 24 | - Change DNS resolver to Cloudflare, Google, Quad9, or a custom resolver | ||
| 25 | |||
| 26 | ## Contributing | ||
| 27 | |||
| 28 | Contributions are welcome. Keep changes scoped, include tests when behavior changes, and open a pull request with a clear summary of the user-facing impact. | ||
| 29 | |||
| 30 | ## Development | ||
| 31 | |||
| 32 | ### Requirements | ||
| 33 | |||
| 34 | - Xcode with current iOS SDK support | ||
| 35 | - iOS Simulator or physical iOS device | ||
| 36 | |||
| 37 | ### Getting Started | ||
| 38 | |||
| 39 | 1. Clone the repository: | ||
| 40 | ```sh | ||
| 41 | git clone https://git.sr.ht/~ccleberg/DomainDig | ||
| 42 | ``` | ||
| 43 | 2. Open the project in Xcode. | ||
| 44 | 3. Build and run the app on a simulator or device. | ||
| 45 | |||
| 46 | ## Security | ||
| 47 | |||
| 48 | If you discover a security issue, see SECURITY.md. | ||
| 49 | |||
| 50 | ## License | ||
| 51 | |||
| 52 | This project is licensed under the GPL 3.0 or later. See LICENSE. | ||
| 53 | |||
| 54 | ## Contact | ||
| 55 | |||
| 56 | Questions or feedback: hello@cleberg.net | ||
SECURITY.md added +33
| @@ -0,0 +1,33 @@ | |||
| 1 | # Security Policy | ||
| 2 | |||
| 3 | ## Supported Versions | ||
| 4 | |||
| 5 | |Version|Supported| | ||
| 6 | |-------|---------| | ||
| 7 | | 1.x | ✅ Yes | | ||
| 8 | | < 1.0 | ❌ No | | ||
| 9 | |||
| 10 | --- | ||
| 11 | |||
| 12 | ## Reporting a Vulnerability | ||
| 13 | |||
| 14 | If you discover a security vulnerability, **do not open a public issue**. | ||
| 15 | Instead: | ||
| 16 | |||
| 17 | 1. **Email** your report to [security@cleberg.net](mailto:security@cleberg.net). | ||
| 18 | Include: | ||
| 19 | - A detailed description of the vulnerability | ||
| 20 | - Steps to reproduce | ||
| 21 | - Any relevant context (e.g., affected versions, environment) | ||
| 22 | 2. **Response Time**: We will acknowledge your report within **3 business days** | ||
| 23 | and keep you updated on the progress. | ||
| 24 | 3. **Resolution**: If confirmed, we will: | ||
| 25 | - Provide an estimated timeline for a fix | ||
| 26 | - Work with you to verify the resolution | ||
| 27 | - Credit you for the discovery (if you wish) | ||
| 28 | 4. **Declined Reports**: If the report is invalid or out of scope, we will | ||
| 29 | explain why and close the issue. | ||
| 30 | |||
| 31 | --- | ||
| 32 | |||
| 33 | **Thank you for helping improve the security of our project!** | ||