Domain > sigkill.com

More information on this domain is in AlienVault OTX

DNS Resolutions

Date	IP Address
2015-02-19	64.71.189.187 (ClassC)
2020-08-05	13.35.118.7 (ClassC)
2020-08-10	99.84.156.2 (ClassC)
2024-04-23	204.246.191.36 (ClassC)
2024-08-20	99.84.66.77 (ClassC)
2024-09-19	99.84.66.4 (ClassC)
2025-01-07	3.163.165.60 (ClassC)
2025-01-25	3.163.165.46 (ClassC)
2025-02-26	99.84.66.108 (ClassC)
2026-02-09	3.169.173.20 (ClassC)

HTTP/1.1 200 OKContent-Type: text/htmlContent-Length: 4409Connection: keep-aliveDate: Mon, 22 Apr 2024 21:51:30 GMTLast-Modified: Sun, 16 Jul 2023 20:38:26 GMTETag: 7642e4b9325cc4d93fcf04c8710d3998Ser

html>head>!-- Google tag (gtag.js) -->script async srchttps://www.googletagmanager.com/gtag/js?idG-XDF79L9NJ1>/script>script>  window.dataLayer  window.dataLayer || ;  function gtag(){dataLayer.push(arguments);}  gtag(js, new Date());  gtag(config, G-XDF79L9NJ1);/script>title>killall -KILL sigkill.com/title>body bgcolor#ffffff text#000000>!-- Just so no one gets pissed off... except SCO... fuck them./* *  linux/arch/i386/kernel/signal.c 2.4.22 version * *  Copyright (C) 1991, 1992  Linus Torvalds * *  1997-11-28  Modified for POSIX.1b signals by Richard Henderson *  2000-06-20  Pentium III FXSR, SSE support by Gareth Hughes */-->pre>tt>/* * Note that init is a special process: it doesnt get signals it doesnt * want to handle. Thus you cannot kill init even with a b>SIGKILL/b> even by * mistake. */int do_signal(struct pt_regs *regs, sigset_t *oldset){	siginfo_t info;	struct k_sigaction *ka;	/*	 * We want the common case to go fast, which	 * is why we may in certain cases get here from	 * kernel mode. Just return without doing anything	 * if so.	 */	if ((regs->xcs & 3) ! 3)		return 1;	if (!oldset)		oldset  &current->blocked;	for (;;) {		unsigned long signr;		spin_lock_irq(&current->sigmask_lock);		signr  dequeue_signal(&current->blocked, &info);		spin_unlock_irq(&current->sigmask_lock);		if (!signr)			break;		if ((current->ptrace & PT_PTRACED) && signr ! b>SIGKILL/b>) {			/* Let the debugger run.  */			current->exit_code  signr;			current->state  TASK_STOPPED;			notify_parent(current, SIGCHLD);			schedule();			/* Were back.  Did the debugger cancel the sig?  */			if (!(signr  current->exit_code))				continue;			current->exit_code  0;			/* The debugger continued.  Ignore SIGSTOP.  */			if (signr  SIGSTOP)				continue;			/* Update the siginfo structure.  Is this good?  */			if (signr ! info.si_signo) {				info.si_signo  signr;				info.si_errno  0;				info.si_code  SI_USER;				info.si_pid  current->p_pptr->pid;				info.si_uid  current->p_pptr-&

View on OTX | View on ThreatMiner

Data with thanks to AlienVault OTX, VirusTotal, Malwr and others. [Sitemap]

Domain > sigkill.com

Is this malicious?

DNS Resolutions

Port 80

Port 443