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: New Zealand

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

;; QUESTION SECTION:
;114.23.106.148.			IN	A

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

;; Query time: 56 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Mar 04 22:08:14 CST 2022
;; MSG SIZE  rcvd: 107
Host info
Host 148.106.23.114.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 148.106.23.114.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
194.190.67.209 attackspambots
Honeypot attack, port: 445, PTR: PTR record not found
2020-09-07 23:04:33
191.102.156.164 attack
(From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question…

My name’s Eric, I found wattfamilychiropractic.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 softw
2020-09-07 23:31:53
200.54.51.124 attackspam
Sep  7 03:49:35 george sshd[1447]: Failed password for invalid user alicia from 200.54.51.124 port 41948 ssh2
Sep  7 03:51:07 george sshd[1480]: Invalid user shorty13 from 200.54.51.124 port 34278
Sep  7 03:51:07 george sshd[1480]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=200.54.51.124 
Sep  7 03:51:09 george sshd[1480]: Failed password for invalid user shorty13 from 200.54.51.124 port 34278 ssh2
Sep  7 03:52:39 george sshd[1487]: Invalid user evil from 200.54.51.124 port 54822
...
2020-09-07 23:24:13
45.118.34.143 attackspam
Aug 28 23:40:04 mail.srvfarm.net postfix/smtpd[2532831]: warning: unknown[45.118.34.143]: SASL PLAIN authentication failed: 
Aug 28 23:40:04 mail.srvfarm.net postfix/smtpd[2532831]: lost connection after AUTH from unknown[45.118.34.143]
Aug 28 23:40:22 mail.srvfarm.net postfix/smtps/smtpd[2528404]: warning: unknown[45.118.34.143]: SASL PLAIN authentication failed: 
Aug 28 23:40:23 mail.srvfarm.net postfix/smtps/smtpd[2528404]: lost connection after AUTH from unknown[45.118.34.143]
Aug 28 23:41:27 mail.srvfarm.net postfix/smtpd[2532518]: warning: unknown[45.118.34.143]: SASL PLAIN authentication failed:
2020-09-07 23:25:48
218.92.0.248 attackbots
(sshd) Failed SSH login from 218.92.0.248 (CN/China/-): 5 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Sep  7 17:16:36 amsweb01 sshd[14141]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=218.92.0.248  user=root
Sep  7 17:16:38 amsweb01 sshd[14141]: Failed password for root from 218.92.0.248 port 35537 ssh2
Sep  7 17:16:42 amsweb01 sshd[14141]: Failed password for root from 218.92.0.248 port 35537 ssh2
Sep  7 17:16:46 amsweb01 sshd[14141]: Failed password for root from 218.92.0.248 port 35537 ssh2
Sep  7 17:16:52 amsweb01 sshd[14141]: Failed password for root from 218.92.0.248 port 35537 ssh2
2020-09-07 23:36:11
64.227.0.92 attackspambots
invalid user
2020-09-07 23:26:55
114.33.57.215 attack
port scan and connect, tcp 23 (telnet)
2020-09-07 23:47:04
190.199.246.243 attackbots
Icarus honeypot on github
2020-09-07 23:27:25
51.75.95.185 attack
Motherfucking OVH criminal pieces of shit again.
2020-09-07 23:49:50
95.111.254.1 attackspambots
Automatic report - XMLRPC Attack
2020-09-07 23:45:49
122.163.126.206 attackbotsspam
Unauthorized SSH login attempts
2020-09-07 23:22:57
92.223.105.154 attackbots
Failed password for root from 92.223.105.154 port 60038 ssh2
Invalid user oracle from 92.223.105.154 port 37776
pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=mad-projects.online
Invalid user oracle from 92.223.105.154 port 37776
Failed password for invalid user oracle from 92.223.105.154 port 37776 ssh2
2020-09-07 23:54:27
51.75.122.213 attackspambots
Sep  7 02:27:34 pixelmemory sshd[35239]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.122.213  user=root
Sep  7 02:27:36 pixelmemory sshd[35239]: Failed password for root from 51.75.122.213 port 56394 ssh2
Sep  7 02:29:02 pixelmemory sshd[35347]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.75.122.213  user=root
Sep  7 02:29:05 pixelmemory sshd[35347]: Failed password for root from 51.75.122.213 port 52114 ssh2
Sep  7 02:30:30 pixelmemory sshd[35593]: Invalid user engler from 51.75.122.213 port 47838
...
2020-09-07 23:18:26
192.3.199.170 attackbots
Sep  7 16:34:36 router sshd[5355]: Failed password for root from 192.3.199.170 port 47253 ssh2
Sep  7 16:34:36 router sshd[5357]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=192.3.199.170 
...
2020-09-07 23:25:06
112.133.251.60 attackbots
Unauthorised login to NAS
2020-09-07 23:16:04

Recently Reported IPs

114.23.105.187 114.23.106.4 114.23.107.36 114.23.118.157
117.66.174.207 117.66.174.228 117.66.174.227 117.66.174.211
117.66.174.202 117.66.174.200 114.23.118.217 117.66.174.229
117.66.174.188 117.66.174.186 117.66.174.221 117.66.174.230
117.66.174.239 117.66.174.241 117.66.174.240 117.66.174.250