On 2026-10-11 the domain kitchenraja.in returned an HTTP status code 200, recording a successful server response at that time. The observed server header was DPS/2.0.0+sha-ed47954.
Recorded Evidence
PhishDestroy internally listed kitchenraja.in on 2026-10-11. OTX documented 36 pulses referencing the domain on 2026-10-11. URLScan captured a report for kitchenraja.in on 2026-10-10. The registrar recorded for kitchenraja.in is GoDaddy with a registration date of 2025-05-20.
Interpretation
PhishDestroy contains a listing entry for kitchenraja.in, measuring an internal catalogue indicator. The HTTP status describes a single technical observation of the domain’s response. OTX pulses provide a count of external intelligence entries associated with the domain.
Recommended Actions
Retain the HTTP status record, the PhishDestroy listing, and the OTX pulses for kitchenraja.in to enable future comparisons. Use the URLScan report alongside these dated observations to review any changes in listings or technical behavior over time.
Certificate hostname mismatch·
発行者 GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1· stored validity ends in 172 days
Network & certificates
Stored technical evidence
Network & DNS
Resolved IP
76.223.105.230
Network ASN
AS16509
Organization
Amazon.com, Inc.
Observed location
Seattle, US
Server header
DPS/2.0.0+sha-ed47954
ネームサーバー 2
ns21.domaincontrol.com
ns22.domaincontrol.com
Location describes the IP network.
TLS証明書
Issuer
GoDaddy.com / GoDaddy TLS Intermediate CA DV - R1v1
Valid from
2026-09-16 07:03:48
Valid until
2027-04-02 07:03:48
Hostname coverage
Certificate hostname mismatch
Validity
Within stored validity dates
Collection time
2026-10-10 22:02:04 UTC
Collection source
PhishDestroy collector
Certificate fingerprint6eac99ecdd94c3912e4aca3df304f7dbb599173d979303cee4f904b60bfd66bfCertificate names · 1 SANs
www.kitchenraja.in
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: StaleRegistration: Unknown
Latest HTTP observationコンテンツ公開中Ordinary HTTP content served90%2026-10-10 23:02:14 UTC
RDAP registration不明
Observed timelinelast reachable: 2026-10-10 23:02:14 UTClast content: 2026-10-10 23:02:14 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 21:36:09 UTC
Domain ingestion complete. Initial state is marked as alive pointing to IP 76.223.105.230.
脅威対応 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.
(IN)
