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.
탐지 회피 분석
클로킹 및 트래픽 분산 점검
아직 스캔되지 않았습니다크롤러와 브라우저 간의 차이는 아직 보고된 바가 없습니다.
이 호스트에 대해 저장된 크롤러 대 브라우저 관측 데이터와, 케이타로 스타일의 트래픽 분배 시스템을 위한 실시간 지문 확인 정보.
IP 평판abuse score 28/10030 reportsFraud OrdersFTP Brute-ForcePhishingOpen ProxyWeb SpamEmail SpamPort ScanHackingSpoofingBrute-ForceBad Web Botchecked 2026년 10월 11일
OTX Tags2026-10activeall-domainsblocklistcontentcryptocyber security도메인drainerfraudioclivelokibotlokipws+6 more
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: ResolvedRegistration: Unknown
Latest HTTP observation활성 콘텐츠Ordinary HTTP content served90%2026-10-11 10:00:24 UTC
RDAP registration알 수 없음
Observed timelinelast reachable: 2026-10-11 10:00:24 UTClast content: 2026-10-11 10:00:24 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.
도메인은 계속 연결 가능하거나 액세스가 제한되어 있습니다. 향후 점검을 통해 이 관찰 내용이 업데이트될 수 있습니다.
How we investigate & report
Public scans, evidence and abuse channels
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)
