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

Internet Service Provider: Elisa

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

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;194.211.31.45.			IN	A

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

;; Query time: 105 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Wed Sep 25 03:44:50 CST 2019
;; MSG SIZE  rcvd: 117
Host info
Host 45.31.211.194.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

** server can't find 45.31.211.194.in-addr.arpa: NXDOMAIN

Related IP info:
Related comments:
IP Type Details Datetime
222.186.175.150 attackbots
2019-09-29 UTC: 10x - (10x)
2019-09-30 17:57:27
23.250.36.89 attackbotsspam
(From BillGrant0124@gmail.com) Hi!

Do you want your website to start performing better on Google? The fact of the matter is that every website needs to be optimized before it can attain its full potential out on the Web. Your website is definitely no exception - but here's the good news. 

With a few key feature upgrades and inspections of your website's structure and code, we can get it up to spec. You can begin demolishing your competition - even the ones that have been around for years. It's definitely not impossible. Remember: if you're not on the first page, then you might be missing a lot of business opportunities. We can work together to help you reach the top.

I'm offering you a free consultation, so I can show you how the optimization can make your website rank higher on Google and other search engines. Kindly let me know if you're interested, so I can give you a call at a time that works best for you. I hope to speak with you soon.

Thank you.
Bill Grant
2019-09-30 17:59:59
85.214.36.244 attackspam
Sep 30 08:34:08 *** sshd[16630]: Invalid user Xerces from 85.214.36.244
2019-09-30 18:15:12
106.51.26.164 attackbotsspam
PHI,WP GET /wp-login.php
2019-09-30 17:50:00
134.175.151.155 attackbots
Sep 30 08:12:56 OPSO sshd\[22738\]: Invalid user solr from 134.175.151.155 port 40920
Sep 30 08:12:56 OPSO sshd\[22738\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.151.155
Sep 30 08:12:59 OPSO sshd\[22738\]: Failed password for invalid user solr from 134.175.151.155 port 40920 ssh2
Sep 30 08:18:19 OPSO sshd\[24185\]: Invalid user john from 134.175.151.155 port 52478
Sep 30 08:18:19 OPSO sshd\[24185\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.175.151.155
2019-09-30 18:14:56
178.128.42.36 attackspam
Sep 30 11:13:02 vmd17057 sshd\[6648\]: Invalid user clerk from 178.128.42.36 port 33010
Sep 30 11:13:02 vmd17057 sshd\[6648\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.42.36
Sep 30 11:13:04 vmd17057 sshd\[6648\]: Failed password for invalid user clerk from 178.128.42.36 port 33010 ssh2
...
2019-09-30 17:42:44
192.42.116.16 attackbots
Sep 30 10:26:07 rotator sshd\[10813\]: Failed password for root from 192.42.116.16 port 49472 ssh2Sep 30 10:26:09 rotator sshd\[10813\]: Failed password for root from 192.42.116.16 port 49472 ssh2Sep 30 10:26:11 rotator sshd\[10813\]: Failed password for root from 192.42.116.16 port 49472 ssh2Sep 30 10:26:14 rotator sshd\[10813\]: Failed password for root from 192.42.116.16 port 49472 ssh2Sep 30 10:26:16 rotator sshd\[10813\]: Failed password for root from 192.42.116.16 port 49472 ssh2Sep 30 10:26:19 rotator sshd\[10813\]: Failed password for root from 192.42.116.16 port 49472 ssh2
...
2019-09-30 17:47:48
2606:4700:30::681f:4ade attack
Sep 30 03:53:11   DDOS Attack: SRC=2606:4700:0030:0000:0000:0000:681f:4ade DST=[Masked] LEN=72 TC=0 HOPLIMIT=60 FLOWLBL=885598 PROTO=TCP SPT=443 DPT=37154 WINDOW=27200 RES=0x00 ACK SYN URGP=0
2019-09-30 17:35:53
159.65.97.238 attackspam
Sep 30 11:38:01 bouncer sshd\[19120\]: Invalid user ramon from 159.65.97.238 port 49102
Sep 30 11:38:01 bouncer sshd\[19120\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=159.65.97.238 
Sep 30 11:38:03 bouncer sshd\[19120\]: Failed password for invalid user ramon from 159.65.97.238 port 49102 ssh2
...
2019-09-30 18:14:39
45.55.222.162 attack
ssh brute force
2019-09-30 18:00:27
139.199.14.128 attack
$f2bV_matches
2019-09-30 18:01:31
91.236.239.228 attack
CloudCIX Reconnaissance Scan Detected, PTR: lam58.firstheberg.net.
2019-09-30 17:37:17
185.56.81.41 attack
firewall-block, port(s): 5900/tcp
2019-09-30 17:50:12
139.199.168.184 attack
Sep 30 11:54:04 mail sshd\[15063\]: Invalid user web1 from 139.199.168.184 port 46936
Sep 30 11:54:04 mail sshd\[15063\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.168.184
Sep 30 11:54:06 mail sshd\[15063\]: Failed password for invalid user web1 from 139.199.168.184 port 46936 ssh2
Sep 30 11:59:10 mail sshd\[16014\]: Invalid user debian from 139.199.168.184 port 57968
Sep 30 11:59:10 mail sshd\[16014\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=139.199.168.184
2019-09-30 18:08:07
171.67.70.91 attack
Here more information about 171.67.70.91 
info: [Unhostnameed States] 32 Stanford Univershostnamey 
DNS: research.esrg.stanford.edu 
Connected: 6 servere(s) 
Reason: ssh 
Portscan/portflood
Ports: 22,110,1433 
Services: ssh,pop3,ms-sql-s 
servere: Europe/Moscow (UTC+3) 
Found at blocklist: abuseIPDB.com
myIP:89.179.244.250 
 
[2019-09-28 12:29:09] (tcp) myIP:22 <- 171.67.70.91:40976
[2019-09-28 15:04:23] (tcp) myIP:110 <- 171.67.70.91:45445
[2019-09-28 16:21:56] (tcp) myIP:1433 <- 171.67.70.91:43447
[2019-09-29 12:29:06] (tcp) myIP:22 <- 171.67.70.91:37034
[2019-09-29 15:04:23] (tcp) myIP:110 <- 171.67.70.91:35696
[2019-09-29 16:21:57] (tcp) myIP:1433 <- 171.67.70.91:53933


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=171.67.70.91
2019-09-30 17:45:51

Recently Reported IPs

103.133.176.184 64.213.166.120 107.1.125.74 82.26.166.175
87.26.159.132 164.0.132.194 70.60.128.41 69.122.95.47
107.142.68.233 79.181.237.60 98.171.160.93 14.198.148.10
60.67.220.52 114.232.218.164 49.70.102.159 69.78.66.157
79.18.104.214 166.86.132.130 178.156.202.83 123.53.196.215