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

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

;; QUESTION SECTION:
;122.138.148.18.			IN	A

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

;; Query time: 28 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Thu Mar 10 01:30:37 CST 2022
;; MSG SIZE  rcvd: 107
Host info
18.148.138.122.in-addr.arpa domain name pointer 18.148.138.122.adsl-pool.jlccptt.net.cn.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
18.148.138.122.in-addr.arpa	name = 18.148.138.122.adsl-pool.jlccptt.net.cn.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
95.71.224.160 attackspambots
Attempted connection to port 445.
2020-09-03 15:29:49
106.110.46.42 attack
Automatic report - Banned IP Access
2020-09-03 15:17:14
80.82.68.218 attackbots
Attempted connection to port 3389.
2020-09-03 15:30:16
144.76.96.236 attackspam
20 attempts against mh-misbehave-ban on leaf
2020-09-03 15:26:45
197.50.153.241 attackspam
Attempted connection to ports 445, 1433.
2020-09-03 15:41:30
200.186.50.242 attackspambots
Unauthorized connection attempt from IP address 200.186.50.242 on Port 445(SMB)
2020-09-03 15:15:57
103.72.144.228 attackbotsspam
Invalid user nas from 103.72.144.228 port 48750
2020-09-03 15:51:48
41.239.9.136 attackspam
Attempted connection to port 23.
2020-09-03 15:39:18
88.147.152.146 attack
srvr1: (mod_security) mod_security (id:920350) triggered by 88.147.152.146 (RU/-/88-147-152-146.dynamic.152.147.88.in-addr.arpa): 1 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_MODSEC; Logs: 2020/09/03 06:32:36 [error] 194005#0: *337763 [client 88.147.152.146] ModSecurity: Access denied with code 406 (phase 2). Matched "Operator `Rx' with parameter `^[\d.:]+$' against variable `REQUEST_HEADERS:Host'  [redacted] [file "/etc/modsecurity.d/REQUEST-920-PROTOCOL-ENFORCEMENT.conf"] [line "718"] [id "920350"] [rev ""] [msg "Host header is a numeric IP address"] [redacted] [severity "4"] [ver "OWASP_CRS/3.3.0"] [maturity "0"] [accuracy "0"] [tag "application-multi"] [tag "language-multi"] [tag "platform-multi"] [tag "attack-protocol"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/210/272"] [tag "PCI/6.5.10"] [redacted] [uri "/"] [unique_id "159911475637.598198"] [ref "o0,16v21,16"], client: 88.147.152.146, [redacted] request: "GET / HTTP/1.1" [redacted]
2020-09-03 15:11:05
86.213.63.181 attackspam
Invalid user ubuntu from 86.213.63.181 port 40038
2020-09-03 15:13:50
45.55.61.114 attackspam
"XSS Attack Detected via libinjection - Matched Data: XSS data found within ARGS_NAMES:
2020-09-03 15:12:09
58.62.207.50 attackbots
Invalid user resolve from 58.62.207.50 port 11434
2020-09-03 15:19:32
177.10.241.126 attackspam
Autoban   177.10.241.126 AUTH/CONNECT
2020-09-03 15:11:20
190.131.220.2 attackbotsspam
20/9/3@02:19:45: FAIL: Alarm-Network address from=190.131.220.2
...
2020-09-03 15:43:20
180.100.206.35 attackbotsspam
Attempted connection to port 32292.
2020-09-03 15:46:58

Recently Reported IPs

122.138.147.98 122.138.149.173 122.138.155.107 122.138.155.118
122.138.155.140 122.138.155.148 122.138.155.165 122.138.155.166
122.138.155.176 122.138.155.178 122.138.155.182 122.138.155.190
122.138.155.193 122.138.155.203 122.138.155.215 122.138.155.218
122.138.155.222 122.138.155.225 122.138.155.25 122.138.155.253