Must be a valid IPv4 or IPv6 ip address, e.g. 127.0.0.1 or 2001:DB8:0:0:8:800:200C:417A
Basic Info

City: Houston

Region: Texas

Country: United States

Internet Service Provider: unknown

Hostname: unknown

Organization: unknown

Usage Type: unknown

Comments:
No discussion about this IP yet. Click above link to make one.
Comments on same subnet:
No discussion about this subnet yet..
Whois info:
b
Dig info:
; <<>> DiG 9.10.3-P4-Ubuntu <<>> 4.59.107.42
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 20548
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;4.59.107.42.			IN	A

;; AUTHORITY SECTION:
.			537	IN	SOA	a.root-servers.net. nstld.verisign-grs.com. 2020052602 1800 900 604800 86400

;; Query time: 104 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed May 27 07:39:37 CST 2020
;; MSG SIZE  rcvd: 115
Host info
Host 42.107.59.4.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 42.107.59.4.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
159.253.25.197 attack
firewall-block, port(s): 1900/udp
2019-10-04 18:31:36
141.98.10.62 attackbotsspam
Rude login attack (5 tries in 1d)
2019-10-04 18:55:55
208.91.197.27 attackspambots
utopia.net Ransomware coming through Comcast EPON equipment. Noticed it communicating VIA SNMP when running a packet capture on Win7 box. Norton caught it at first as Malicious Domain Request 21. Now Norton isn't flagging this anymore!!!
2019-10-04 18:53:42
163.44.194.62 attackbotsspam
Automatic report - Banned IP Access
2019-10-04 18:45:08
51.75.202.120 attackspambots
2019-10-04T11:58:52.494517  sshd[14537]: Invalid user Azur123 from 51.75.202.120 port 41806
2019-10-04T11:58:52.507269  sshd[14537]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.202.120
2019-10-04T11:58:52.494517  sshd[14537]: Invalid user Azur123 from 51.75.202.120 port 41806
2019-10-04T11:58:54.836508  sshd[14537]: Failed password for invalid user Azur123 from 51.75.202.120 port 41806 ssh2
2019-10-04T12:02:44.600175  sshd[14625]: Invalid user ZaQ1XsW2 from 51.75.202.120 port 33800
...
2019-10-04 18:22:59
83.48.89.147 attackspambots
Oct  4 06:40:36 www sshd\[48780\]: Failed password for root from 83.48.89.147 port 51682 ssh2Oct  4 06:45:23 www sshd\[49037\]: Failed password for root from 83.48.89.147 port 43261 ssh2Oct  4 06:49:57 www sshd\[49398\]: Failed password for root from 83.48.89.147 port 34840 ssh2
...
2019-10-04 19:01:50
200.206.50.66 attackbotsspam
xmlrpc attack
2019-10-04 18:44:47
211.59.36.66 attack
Brute force attempt
2019-10-04 18:59:34
106.51.98.159 attack
SSH invalid-user multiple login try
2019-10-04 18:58:22
207.154.229.50 attackspambots
Invalid user postgres from 207.154.229.50 port 38436
2019-10-04 18:46:37
178.128.194.116 attackspambots
Invalid user bash from 178.128.194.116 port 55944
2019-10-04 18:41:09
121.67.246.132 attackbots
Oct  4 07:09:50 www2 sshd\[36917\]: Invalid user P@$$word@1234 from 121.67.246.132Oct  4 07:09:52 www2 sshd\[36917\]: Failed password for invalid user P@$$word@1234 from 121.67.246.132 port 54904 ssh2Oct  4 07:14:36 www2 sshd\[37524\]: Invalid user Admin1@3 from 121.67.246.132
...
2019-10-04 18:37:29
193.29.15.60 attack
MultiHost/MultiPort Probe, Scan, Hack -
2019-10-04 18:38:12
187.16.39.88 attackbots
Chat Spam
2019-10-04 18:42:41
119.135.192.111 attackspambots
firewall-block, port(s): 23/tcp
2019-10-04 18:43:52

Recently Reported IPs

98.98.202.212 200.165.72.101 167.250.91.238 171.69.232.203
8.44.134.57 193.137.216.90 182.84.124.145 207.136.6.72
146.241.105.255 112.244.22.97 181.52.173.45 120.157.2.97
52.228.8.254 5.145.108.245 73.45.171.50 99.131.23.71
85.80.194.50 217.112.142.14 212.67.188.106 184.230.131.96