codnit.com was first observed on 2026-10-11, with a PhishDestroy internal listing dated 2026-10-10 documenting its presence as a security indicator. The domain’s registration with NAMECHEAP INC on 2025-07-14 adds context to its timeline and administrative history.
Recorded Evidence
PhishDestroy internal listing records codnit.com as a security indicator on 2026-10-10. The domain was registered with NAMECHEAP INC on 2025-07-14, and first observed on 2026-10-11. These records provide dated evidence from multiple sources regarding the domain’s profile.
Interpretation
PhishDestroy provides a measurement of codnit.com’s status as a security indicator, documenting its inclusion in the internal catalogue. This record offers a reference point for tracking the domain within the publisher’s intelligence system and supports comparison with other dated observations. The timeline established by registration and observation dates allows for contextual review of the domain’s recorded activity.
Recommended Actions
Retain the PhishDestroy internal listing for codnit.com as a reference for ongoing analysis. Compare future PhishDestroy records to identify any changes in catalogue status. Use the domain’s registration and observation dates to inform periodic reviews and update domain security assessments as new evidence becomes available.
DOM Analysisanalyzed 2026年10月11日score 63/1006 brand signals
Submitted URLhttp://codnit.com/
Favicon Hash
ケース ID
ページタイトル
Codnit — Custom Software Development in Austin, TX
Impersonates
ChaseCompoundGoogleScrollShopifySlack
TLS証明書
Certificate hostname mismatch·
発行者 Google Trust Services / WE1· stored validity ends in 73 days
Network & certificates
Stored technical evidence
Network & DNS
Shared CDN edge
Resolved IP
188.114.96.3
Network ASN
AS13335
Organization
Cloudflare, Inc.
Observed location
San Francisco, US
Server header
cloudflare
Edge-IP の評判はこのドメインに起因しません。
ネームサーバー 2
benedict.ns.cloudflare.com
zita.ns.cloudflare.com
Mail routing 2 MX records
mx1.privateemail.compriority 10
mx2.privateemail.compriority 10
Location describes the IP network.
TLS証明書
Issuer
Google Trust Services / WE1
Valid from
2026-09-25 02:27:18
Valid until
2026-12-24 03:27:15
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-11 01:02:12 UTC
Collection source
PhishDestroy collector
Certificate fingerprint985db299a277856e34d76b0b469f44f6e12fcd9ce92f82c14fe790d595ee7191Certificate names · 1 SANs
www.codnit.com
Saved certificate metadata. Certificate dates without a timezone are shown as stored. Transport encryption does not establish that the site is trustworthy.
Evidence layersAvailability: Content servingContent: Content served at rootDNS: ResolvedRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-11 10:00:28 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-11 10:00:28 UTClast content: 2026-10-11 10:00:28 UTC
Availability, content, DNS and registration are independent evidence layers. NXDOMAIN, an unreachable origin or missing content alone does not prove registrar action. A registrar or provider is credited only when a direct technical marker identifies that actor. Report causality is shown separately.
This timeline displays historical security and status checkpoints observed by the PhishDestroy automated monitoring network. It records domain lifecycle updates, scanner changes, and threat telemetry over time.
Threat First Observed2026-10-10 23:15:57 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 188.114.96.3.
脅威対応 Pipeline
ディスカバリー
Analysis
Notifications
Monitoring
8 recorded events. These records describe collected evidence, outgoing notifications and publication; they do not confirm a complete investigation or a takedown.
We scan suspicious URLs, inspect public results and send evidence through the appropriate abuse-reporting channels. The dated events above show what is recorded for this domain. The directory below explains the wider workflow.
01Public scans & evidence collection10 sources and tool groups+
Inspect the public DNS, TLS, HTTP and technology surface.
02Abuse reports & follow-upRegistrar, hosting and security channels+
Identify the responsible provider. Match registration and hosting records to the relevant abuse contact.
Prepare an evidence package. Include the URL, public scan references, captures and the recorded observations.
Send the report. Keep outgoing report records and recipient information when available.
Recheck and publish updates. Track later scanner verdicts, provider responses and site availability.
Security services used for scanning, reputation checks and reporting are listed below. A service being listed is not evidence that it received, accepted or acted on this particular domain. Recorded submissions appear in the notification history above.
(US)
