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: unknown

Region: unknown

Country: South Africa

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 <<>> 196.216.138.2
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27548
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;196.216.138.2.			IN	A

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

;; Query time: 22 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 13 16:21:55 CST 2022
;; MSG SIZE  rcvd: 106
Host info
Host 2.138.216.196.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 2.138.216.196.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
80.82.67.167 attack
22/tcp 22/tcp 22/tcp...
[2020-02-05/03-07]4pkt,1pt.(tcp)
2020-03-07 17:35:21
64.94.208.204 attackspambots
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found drmcatamney.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well.

So here’s my question – what happens AFTER someone lands on your site?  Anything?

Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever.

That means that all the work and effort you put into getting them to show up, goes down the tubes.

Why would you want all that good work – and the great site you’ve built – go to waste?

Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry.

But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket?
  
You can – thanks to revolutionary new software that ca
2020-03-07 17:15:54
192.241.230.4 attackspam
firewall-block, port(s): 55718/tcp
2020-03-07 17:33:48
185.36.81.57 attackspam
Mar  7 10:12:38 srv01 postfix/smtpd\[15386\]: warning: unknown\[185.36.81.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  7 10:12:43 srv01 postfix/smtpd\[6013\]: warning: unknown\[185.36.81.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  7 10:13:09 srv01 postfix/smtpd\[6013\]: warning: unknown\[185.36.81.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  7 10:15:36 srv01 postfix/smtpd\[6013\]: warning: unknown\[185.36.81.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
Mar  7 10:16:45 srv01 postfix/smtpd\[15416\]: warning: unknown\[185.36.81.57\]: SASL LOGIN authentication failed: UGFzc3dvcmQ6
...
2020-03-07 17:18:34
123.170.33.182 attackbotsspam
Honeypot attack, port: 5555, PTR: PTR record not found
2020-03-07 17:17:06
111.250.185.1 attackspam
Mar  7 05:53:15 h1745522 proftpd[24081]: 0.0.0.0 (111.250.185.1[111.250.185.1]) - USER anonymous: no such user found from 111.250.185.1 [111.250.185.1] to 85.214.254.6:21
Mar  7 05:53:17 h1745522 proftpd[24082]: 0.0.0.0 (111.250.185.1[111.250.185.1]) - USER www: no such user found from 111.250.185.1 [111.250.185.1] to 85.214.254.6:21
Mar  7 05:53:18 h1745522 proftpd[24083]: 0.0.0.0 (111.250.185.1[111.250.185.1]) - USER www: no such user found from 111.250.185.1 [111.250.185.1] to 85.214.254.6:21
Mar  7 05:53:19 h1745522 proftpd[24084]: 0.0.0.0 (111.250.185.1[111.250.185.1]) - USER paery-huette-lachtal: no such user found from 111.250.185.1 [111.250.185.1] to 85.214.254.6:21
Mar  7 05:53:20 h1745522 proftpd[24085]: 0.0.0.0 (111.250.185.1[111.250.185.1]) - USER paery-huette-lachtal: no such user found from 111.250.185.1 [111.250.185.1] to 85.214.254.6:21
...
2020-03-07 17:32:49
163.172.185.190 attack
Mar  6 22:57:06 prox sshd[652]: Failed password for root from 163.172.185.190 port 52482 ssh2
2020-03-07 17:35:46
157.230.123.253 attack
sshd jail - ssh hack attempt
2020-03-07 17:04:44
89.38.147.65 attack
Mar  6 14:39:16 delbain2 sshd[25076]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.38.147.65  user=r.r
Mar  6 14:39:18 delbain2 sshd[25076]: Failed password for r.r from 89.38.147.65 port 60902 ssh2
Mar  6 14:39:18 delbain2 sshd[25076]: Received disconnect from 89.38.147.65 port 60902:11: Bye Bye [preauth]
Mar  6 14:39:18 delbain2 sshd[25076]: Disconnected from authenticating user r.r 89.38.147.65 port 60902 [preauth]
Mar  6 14:43:12 delbain2 sshd[25252]: Invalid user isl from 89.38.147.65 port 49420
Mar  6 14:43:12 delbain2 sshd[25252]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=89.38.147.65
Mar  6 14:43:14 delbain2 sshd[25252]: Failed password for invalid user isl from 89.38.147.65 port 49420 ssh2
Mar  6 14:43:14 delbain2 sshd[25252]: Received disconnect from 89.38.147.65 port 49420:11: Bye Bye [preauth]
Mar  6 14:43:14 delbain2 sshd[25252]: Disconnected from invalid user isl 89........
-------------------------------
2020-03-07 17:26:53
2.229.123.30 attackbots
unauthorized connection attempt
2020-03-07 17:22:26
86.238.210.123 attackbotsspam
Honeypot attack, port: 5555, PTR: lfbn-idf2-1-979-123.w86-238.abo.wanadoo.fr.
2020-03-07 17:34:56
82.102.21.215 attackbots
Web app attack attempts, scanning for vulnerability.
Date: 2020 Mar 06. 09:19:13
Source IP: 82.102.21.215

Portion of the log(s):
82.102.21.215 - [06/Mar/2020:09:19:12 +0100] "GET /dev/rss/catalog/notifystock HTTP/1.1" 404 169 "-" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0"
82.102.21.215 - [06/Mar/2020:09:19:12 +0100] GET /dev/rss/order/new
82.102.21.215 - [06/Mar/2020:09:19:12 +0100] GET /rss/catalog/review
82.102.21.215 - [06/Mar/2020:09:19:12 +0100] GET /rss/catalog/notifystock
82.102.21.215 - [06/Mar/2020:09:19:12 +0100] GET /rss/order/new
82.102.21.215 - [06/Mar/2020:09:19:11 +0100] GET /staging/index.php/admin/
82.102.21.215 - [06/Mar/2020:09:19:11 +0100] GET /magento/index.php/admin/
82.102.21.215 - [06/Mar/2020:09:19:11 +0100] GET /store/index.php/admin/
82.102.21.215 - [06/Mar/2020:09:19:11 +0100] GET /demo/index.php/admin/
82.102.21.215 - [06/Mar/2020:09:19:10 +0100] GET /shop/index.php/admin/
82.102.21.215 - [06/Mar/2020:09:19:10 +0100] GET /test/
2020-03-07 17:30:53
187.141.71.27 attackbots
Mar  7 09:08:19 sd-53420 sshd\[18344\]: Invalid user toor from 187.141.71.27
Mar  7 09:08:19 sd-53420 sshd\[18344\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.141.71.27
Mar  7 09:08:20 sd-53420 sshd\[18344\]: Failed password for invalid user toor from 187.141.71.27 port 53028 ssh2
Mar  7 09:12:11 sd-53420 sshd\[18765\]: Invalid user aizawa from 187.141.71.27
Mar  7 09:12:11 sd-53420 sshd\[18765\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.141.71.27
...
2020-03-07 17:31:48
219.145.195.240 attackspam
Honeypot attack, port: 445, PTR: PTR record not found
2020-03-07 17:07:26
183.6.102.54 attackspam
unauthorized connection attempt
2020-03-07 17:28:11

Recently Reported IPs

196.217.80.11 196.217.38.15 196.218.114.236 196.218.196.104
196.218.246.252 196.219.102.92 196.218.158.106 196.218.235.32
196.218.156.66 196.219.110.33 196.218.205.52 196.219.72.247
196.219.141.175 196.219.141.86 196.221.149.252 196.220.96.30
196.219.231.98 196.223.119.156 196.221.220.112 196.223.161.126