Skip to content
KitploitKITPLOIT
ツールエクスプロイトブログ
Log in
提出
ツールエクスプロイトブログ
提出

ハッキング、侵入テスト、サイバーセキュリティツールをあなたのセキュリティアーセナルに!

Kitploitはハッキング、サイバーセキュリティ、ペネトレーションテストのツールディレクトリです。最新のプロジェクトアップデートを見つけて、脆弱性の発見、システム分析、テストの自動化、セキュリティの強化を行いましょう。

フィードお問い合わせプライバシー© 2026 Kitploit

ツールディレクトリ

カテゴリ

すべてのカテゴリを見る
Loading categories
Data-Shield_IPv4_Blocklist — Curated IPv4 blocklist of malicious addresses, refreshed every 6 hours for firewall and WAF ingestion, with split lists and CTI-ready formats for threat intelligence platforms. | Kitploit
ツール/GitHubGitHub/duggytuxy/data-shield_ipv4_blocklist
Defensive ToolsIndicator of Compromise (IOC) ManagementThreat Feeds & AggregatorsInformation GatheringWeb SecurityNetwork SecurityThreat IntelligenceIncident Response
GitHubduggytuxy/data-shield_ipv4_blocklist

Data-Shield_IPv4_Blocklist

Curated IPv4 blocklist of malicious addresses, refreshed every 6 hours for firewall and WAF ingestion, with split lists and CTI-ready formats for threat intelligence platforms.

640541053時間22分前Kitploit レビュー済み
共有
リポジトリを見るウェブサイト
要求された言語のコンテンツは利用できません。英語版を表示しています。
Data-Shield IPv4 Blocklists: a shield with a centered D and four IPv4 nodes

Blocklist integrity workflow status Generation scheduled every two hours Latest repository commit GNU GPLv3 license Explore SYSwarden Linux defense Support Data-Shield on Ko-fi

Data-Shield IPv4 Blocklists

Two complete lists. Clear choices. Controlled updates.

Data-Shield provides maintained IPv4 blocklists for inbound filtering on firewalls, gateways and web application firewalls. Choose the policy that fits your environment, import its raw URL, and review its effect on legitimate traffic.

Download standard · Download critical · Report a false positive

Choose your list

ProfileIntended useFile
StandardThe starting point for Internet-facing services, with reviewed exceptions to reduce avoidable blocking.prod_data-shield_ipv4_blocklist.txt
CriticalA broader blocking policy for environments that accept stricter ingress filtering. Review the impact before deployment.prod_critical_data-shield_ipv4_blocklist.txt

Each file is complete and can be used on its own. Applying both lists combines their blocking decisions and may override the exceptions of the profile you intended to use.

The entry count changes over time. Check your product's capacity against the actual file, including whether it silently truncates oversized imports. There is no fixed 100,000-entry cap. Split files are no longer published; existing integrations must use one of the two complete files above.

Stable download URLs

DestinationStandardCritical
GitHubRaw fileRaw file
GitLabRaw fileRaw file
CodebergRaw fileRaw file
BitbucketRaw fileRaw file
jsDelivr CDNRaw fileRaw file

These are the existing download URLs used by SYSwarden. The two filenames and their paths remain unchanged. GitLab manages repository mirroring to Codeberg and Bitbucket. jsDelivr serves a cached copy from GitHub, so CDN refreshes can lag behind publication.

Use a raw file URL in your firewall's feed configuration. A repository or preview-page URL returns a web page, not the blocklist.

Format and updates

  • Plain text, with one public IPv4 address per line.
  • No headers, comments, ports, CIDR ranges or IPv6 entries.
  • Duplicate addresses removed and addresses sorted numerically.
  • Generation scheduled every two hours. A new commit appears only when published file content changes.
  • Both files validated before publication and committed together on GitHub and GitLab. Downstream mirrors and CDN caches can differ until they refresh.
  • Failed generation checks preserve the last validated files. Failed publication is retried independently.

The public repository distributes the lists and their usage documentation. Review a file's commit history to check when its content last changed. Neither a successful download nor an unchanged commit proves that your firewall has applied the latest available data.

Deployment strategy

  1. Start with the standard profile. Check the number of entries and your device's import limits.
  2. Apply the list to inbound Internet traffic. Match the remote source address on traffic reaching the gateway or your published services. Do not apply the feed as a blanket outbound destination blocklist.
  3. Review rule ordering and local exceptions. Preserve required administration and business access. A whitelist must take precedence according to your firewall's own rule model.
  4. Observe before broad enforcement. Use logging or a limited deployment to inspect matches and identify legitimate services that need exceptions.
  5. Refresh and monitor. Configure automatic retrieval where supported. Check fetch failures, truncation warnings and the number of entries actually loaded. Keep the last working rules if a download or import fails.

Platform integration guides

The Data-Shield website documentation provides setup instructions, copyable feed URLs and commands, capacity checks, and verification steps for sixteen platforms:

ツールをダウンロード

人気

すべて見る →

コミュニティで最も使われているツールを見つけましょう。

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 究極のOSINTツールキット:調査グラフ、信頼度スコアリング、エイリアスファミリー、マップ、タイムライン、レポート。49個のモジュール、400以上のサイト、APIキー不要。

    565
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock ワンタップ実行アプリ(CVE-2026-43499)

    478
  • 3

    ARTEX

    baarai/artex

    プランナー/ワーカーエージェント、資産グラフと探索グラフ、MITMトラフィック記録、脆弱性の再テストを備えたLLMマルチエージェント自律ペネトレーションテストプラットフォーム。

    383
  • 4

    redforge

    cybersecurity91/redforge

    ブラウザ側のレッドチームツールキット。偵察、ペイロード生成、認証情報攻撃、暗号、エンコーディング、エンゲージメントレポート向けの102のオフラインツールを備えています。

    327
  • 5

    estorides

    grisuno/estorides

    99以上の無料OSINTソースを並列で集約し、エンティティをナレッジグラフに解決し、LLM支援の分析とともにSTIX 2.1、MISP、またはGraphMLでエクスポートします。

    258
  • 6

    CyberStrikeAI

    ed1s0nz/cyberstrikeai

    AIネイティブなサイバーセキュリティのためのアクションシステム。意図がガバナンスされた実行に変わり、証拠が運用記憶となり、すべての操作が次の操作を改善する。

    256

すべてのツールを探索

ツールコレクションを閲覧

すべてのツールを見る →