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: United States of America (the)

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

;; QUESTION SECTION:
;148.116.22.19.			IN	A

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

;; Query time: 76 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 28 14:32:10 CST 2025
;; MSG SIZE  rcvd: 106
Host info
Host 19.22.116.148.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 19.22.116.148.in-addr.arpa: NXDOMAIN
Related IP info:
Related comments:
IP Type Details Datetime
182.61.48.209 attack
Invalid user guest from 182.61.48.209 port 48212
2019-12-26 20:00:58
101.100.224.39 attackspambots
Dec 26 07:22:29 ns3042688 courier-pop3d: LOGIN FAILED, user=info@cesumin.info, ip=\[::ffff:101.100.224.39\]
...
2019-12-26 19:51:33
139.199.127.60 attackspambots
Dec 26 08:59:08 mout sshd[11642]: Invalid user weenie from 139.199.127.60 port 48926
2019-12-26 19:58:47
185.209.0.92 attack
firewall-block, port(s): 3333/tcp, 3996/tcp, 5555/tcp, 6666/tcp, 7777/tcp, 10000/tcp
2019-12-26 19:36:01
46.197.66.79 attackspam
Automatic report - SSH Brute-Force Attack
2019-12-26 19:28:48
138.197.180.102 attackbots
20 attempts against mh-ssh on cloud.magehost.pro
2019-12-26 19:38:06
182.121.207.128 attackbots
Scanning
2019-12-26 19:45:46
117.176.240.100 attack
Scanning
2019-12-26 20:07:27
134.73.51.48 attack
Postfix DNSBL listed. Trying to send SPAM.
2019-12-26 19:27:30
112.85.42.188 attack
12/26/2019-06:02:40.784281 112.85.42.188 Protocol: 6 ET SCAN Potential SSH Scan
2019-12-26 20:06:38
104.244.79.146 attackbotsspam
2019-12-26T11:53:02.731693shield sshd\[7798\]: Invalid user fake from 104.244.79.146 port 58160
2019-12-26T11:53:02.737580shield sshd\[7798\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.244.79.146
2019-12-26T11:53:04.979596shield sshd\[7798\]: Failed password for invalid user fake from 104.244.79.146 port 58160 ssh2
2019-12-26T11:53:05.775204shield sshd\[7800\]: Invalid user ubnt from 104.244.79.146 port 33856
2019-12-26T11:53:05.779615shield sshd\[7800\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=104.244.79.146
2019-12-26 20:02:17
49.235.212.247 attack
Dec 26 03:22:43 vps46666688 sshd[9385]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.212.247
Dec 26 03:22:45 vps46666688 sshd[9385]: Failed password for invalid user southworth from 49.235.212.247 port 55712 ssh2
...
2019-12-26 19:43:17
198.108.67.49 attackbots
firewall-block, port(s): 8008/tcp
2019-12-26 19:52:33
173.249.21.236 attack
Dec 26 01:40:29 dallas01 sshd[26304]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=173.249.21.236
Dec 26 01:40:32 dallas01 sshd[26304]: Failed password for invalid user mime from 173.249.21.236 port 54520 ssh2
Dec 26 01:46:11 dallas01 sshd[31289]: Failed password for root from 173.249.21.236 port 38296 ssh2
2019-12-26 19:37:46
163.172.39.84 attackspam
Invalid user erin from 163.172.39.84 port 40815
2019-12-26 19:52:45

Recently Reported IPs

205.176.172.159 174.31.161.229 24.116.179.109 205.170.46.193
222.138.215.111 164.248.125.31 31.126.41.212 143.144.137.199
91.140.159.192 22.193.94.25 88.11.198.111 7.15.194.53
89.158.121.137 23.119.25.95 24.254.34.173 9.154.81.136
73.103.37.105 175.169.241.219 242.166.162.52 206.199.71.1