From 6e273c2676ce29cef057d117e4427e031886e743 Mon Sep 17 00:00:00 2001 From: Christian Cleberg Date: Fri, 17 Jul 2026 10:39:17 -0500 Subject: v4.7.0: Add domain reputation/blocklist data source - New DomainReputationResult model (status: clean/listed/unknown, listed sources, checked-at) and a `reputation(domain:)` method on ExternalDataService, mirroring the existing pluggable-URL enrichment pattern (ownership history, DNS history, extended subdomains, pricing). With no endpoint configured (the default; DomainDig ships no bundled third-party reputation dependency) it resolves to unavailable rather than "clean". - New .reputation FeatureCapability/DataCapability, gated Pro+ like domainPricing. - Threaded reputation/reputationError through LookupSnapshot and HistoryEntry (backward-compatible decode) so results persist with history entries. - Auto-fetched in performLookup alongside pricing; surfaced as a "Reputation" info row, folded into DomainInsightEngine's risk score/factors and top-level insights (a listed domain raises risk score and adds a factor/insight), and exported in text, CSV, and JSON report output. - Reputation-driven risk changes ride the existing change-severity pipeline, so a listed status flip is visible to monitoring the same way any other risk delta is, without bespoke monitoring wiring. --- DomainDig/DataAccessService.swift | 2 ++ 1 file changed, 2 insertions(+) (limited to 'DomainDig/DataAccessService.swift') diff --git a/DomainDig/DataAccessService.swift b/DomainDig/DataAccessService.swift index 98e215d..43b664e 100644 --- a/DomainDig/DataAccessService.swift +++ b/DomainDig/DataAccessService.swift @@ -11,6 +11,8 @@ enum DataAccessService { return FeatureAccessService.hasAccess(to: .extendedSubdomains) case .domainPricing: return FeatureAccessService.hasAccess(to: .domainPricing) + case .reputation: + return FeatureAccessService.hasAccess(to: .reputation) } } } -- cgit v1.2.3