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

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

;; QUESTION SECTION:
;199.130.199.9.			IN	A

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

;; Query time: 59 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Aug 08 06:15:40 CST 2023
;; MSG SIZE  rcvd: 106
Host info
Host 9.199.130.199.in-addr.arpa not found: 2(SERVFAIL)
Nslookup info:
server can't find 199.130.199.9.in-addr.arpa: SERVFAIL
Related IP info:
Related comments:
IP Type Details Datetime
51.75.52.127 attackbotsspam
Port scan: Attack repeated for 24 hours
2019-10-26 06:45:56
206.189.35.254 attackbots
Oct 25 23:11:56 server sshd\[19371\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.35.254  user=saslauth
Oct 25 23:11:58 server sshd\[19371\]: Failed password for saslauth from 206.189.35.254 port 46390 ssh2
Oct 25 23:19:17 server sshd\[20673\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.35.254  user=saslauth
Oct 25 23:19:18 server sshd\[20673\]: Failed password for saslauth from 206.189.35.254 port 44566 ssh2
Oct 25 23:26:43 server sshd\[22635\]: Invalid user biblioteca from 206.189.35.254
Oct 25 23:26:43 server sshd\[22635\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=206.189.35.254 
...
2019-10-26 06:19:59
210.36.247.22 attackbots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2019-10-26 06:38:24
202.120.38.28 attackspam
Oct 25 12:09:21 wbs sshd\[11751\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.120.38.28  user=root
Oct 25 12:09:23 wbs sshd\[11751\]: Failed password for root from 202.120.38.28 port 24514 ssh2
Oct 25 12:14:01 wbs sshd\[12129\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.120.38.28  user=root
Oct 25 12:14:03 wbs sshd\[12129\]: Failed password for root from 202.120.38.28 port 33281 ssh2
Oct 25 12:18:42 wbs sshd\[12485\]: Invalid user michael from 202.120.38.28
Oct 25 12:18:42 wbs sshd\[12485\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.120.38.28
2019-10-26 06:28:20
45.136.109.208 attack
Blocked for port scanning.
Time: Fri Oct 25. 18:20:30 2019 +0200
IP: 45.136.109.208 (DE/Germany/-)

Sample of block hits:
Oct 25 18:18:39 vserv kernel: [3185641.907005] Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC= SRC=45.136.109.208 DST=[removed] LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=11664 PROTO=TCP SPT=52593 DPT=5003 WINDOW=1024 RES=0x00 SYN URGP=0
Oct 25 18:18:41 vserv kernel: [3185643.378997] Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC= SRC=45.136.109.208 DST=[removed] LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=13469 PROTO=TCP SPT=52593 DPT=63367 WINDOW=1024 RES=0x00 SYN URGP=0
Oct 25 18:18:56 vserv kernel: [3185658.549821] Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC= SRC=45.136.109.208 DST=[removed] LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=29856 PROTO=TCP SPT=52593 DPT=3448 WINDOW=1024 RES=0x00 SYN URGP=0
Oct 25 18:19:01 vserv kernel: [3185663.635668] Firewall: *TCP_IN Blocked* IN=eth0 OUT= MAC= SRC=45.136.109.208 DST=[removed] LEN=40 TOS=0x00 PREC=0x00 TTL=242 ID=34947 PROTO=TCP SPT=52593 DPT=63394 WINDOW
2019-10-26 06:31:52
64.31.6.82 attack
SIPVicious Scanner Detection
2019-10-26 06:26:38
206.189.166.172 attackspambots
$f2bV_matches
2019-10-26 06:16:11
49.234.25.11 attack
Lines containing failures of 49.234.25.11
Oct 24 22:18:14 shared09 sshd[2478]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.25.11  user=r.r
Oct 24 22:18:16 shared09 sshd[2478]: Failed password for r.r from 49.234.25.11 port 46026 ssh2
Oct 24 22:18:16 shared09 sshd[2478]: Received disconnect from 49.234.25.11 port 46026:11: Bye Bye [preauth]
Oct 24 22:18:16 shared09 sshd[2478]: Disconnected from authenticating user r.r 49.234.25.11 port 46026 [preauth]
Oct 24 22:38:57 shared09 sshd[8657]: Invalid user artemio from 49.234.25.11 port 52768
Oct 24 22:38:57 shared09 sshd[8657]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.234.25.11
Oct 24 22:38:59 shared09 sshd[8657]: Failed password for invalid user artemio from 49.234.25.11 port 52768 ssh2
Oct 24 22:39:00 shared09 sshd[8657]: Received disconnect from 49.234.25.11 port 52768:11: Bye Bye [preauth]
Oct 24 22:39:00 shared09 sshd[8657........
------------------------------
2019-10-26 06:15:43
177.73.170.158 attack
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2019-10-26 06:39:58
151.56.213.19 attackspam
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2019-10-26 06:41:33
94.25.171.170 attackbots
ENG,WP GET /wp-login.php
2019-10-26 06:35:25
149.202.59.85 attack
Oct 25 12:14:38 hanapaa sshd\[18633\]: Invalid user jessica from 149.202.59.85
Oct 25 12:14:38 hanapaa sshd\[18633\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.ip-149-202-59.eu
Oct 25 12:14:40 hanapaa sshd\[18633\]: Failed password for invalid user jessica from 149.202.59.85 port 43347 ssh2
Oct 25 12:18:44 hanapaa sshd\[19006\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=85.ip-149-202-59.eu  user=root
Oct 25 12:18:46 hanapaa sshd\[19006\]: Failed password for root from 149.202.59.85 port 34414 ssh2
2019-10-26 06:34:53
185.136.159.30 attackbots
Automatic report - Banned IP Access
2019-10-26 06:13:19
211.137.68.126 attack
Oct 25 23:28:46 vpn01 sshd[8411]: Failed password for root from 211.137.68.126 port 22672 ssh2
...
2019-10-26 06:12:33
221.122.121.137 attackspambots
ET SCAN Suspicious inbound to MSSQL port 1433 - port: 1433 proto: TCP cat: Potentially Bad Traffic
2019-10-26 06:37:39

Recently Reported IPs

6.124.103.71 159.168.195.198 62.200.35.149 140.254.104.194
184.105.139.0 163.152.121.228 149.129.222.203 13.228.24.148
175.200.234.189 50.77.99.208 128.1.40.175 109.252.166.168
68.34.1.17 185.237.145.85 225.112.121.111 103.70.147.247
54.211.228.244 54.211.228.141 123.149.76.41 44.183.205.106