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

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

;; QUESTION SECTION:
;109.70.87.70.			IN	A

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

;; Query time: 94 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Fri Feb 25 12:56:36 CST 2022
;; MSG SIZE  rcvd: 105
Host info
70.87.70.109.in-addr.arpa domain name pointer www.vlfk.no.
70.87.70.109.in-addr.arpa domain name pointer vlfk.no.
70.87.70.109.in-addr.arpa domain name pointer www.vestlandfylke.no.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
70.87.70.109.in-addr.arpa	name = www.vestlandfylke.no.
70.87.70.109.in-addr.arpa	name = www.vlfk.no.
70.87.70.109.in-addr.arpa	name = vlfk.no.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
45.136.109.215 attack
Oct 28 12:20:19 mc1 kernel: \[3547949.597847\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.109.215 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=23407 PROTO=TCP SPT=43015 DPT=4374 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 28 12:21:33 mc1 kernel: \[3548023.504919\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.109.215 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=243 ID=45819 PROTO=TCP SPT=43015 DPT=5191 WINDOW=1024 RES=0x00 SYN URGP=0 
Oct 28 12:23:18 mc1 kernel: \[3548128.393669\] \[UFW BLOCK\] IN=eth0 OUT= MAC=96:00:00:11:a9:7b:d2:74:7f:6e:37:e3:08:00 SRC=45.136.109.215 DST=159.69.205.51 LEN=40 TOS=0x00 PREC=0x00 TTL=244 ID=5076 PROTO=TCP SPT=43015 DPT=6966 WINDOW=1024 RES=0x00 SYN URGP=0 
...
2019-10-28 19:33:10
37.203.208.3 attackbots
Oct 28 01:39:42 auw2 sshd\[25353\]: Invalid user http from 37.203.208.3
Oct 28 01:39:42 auw2 sshd\[25353\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.203.208.3
Oct 28 01:39:44 auw2 sshd\[25353\]: Failed password for invalid user http from 37.203.208.3 port 53646 ssh2
Oct 28 01:43:47 auw2 sshd\[25658\]: Invalid user cy from 37.203.208.3
Oct 28 01:43:47 auw2 sshd\[25658\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=37.203.208.3
2019-10-28 19:51:20
93.116.235.14 attack
Unauthorized SMTP/IMAP/POP3 connection attempt
2019-10-28 19:16:55
170.150.155.102 attack
SSH invalid-user multiple login try
2019-10-28 19:46:56
122.228.89.95 attackbots
Oct 28 08:14:39 firewall sshd[32103]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=122.228.89.95  user=root
Oct 28 08:14:41 firewall sshd[32103]: Failed password for root from 122.228.89.95 port 31877 ssh2
Oct 28 08:19:16 firewall sshd[32218]: Invalid user com from 122.228.89.95
...
2019-10-28 19:49:58
113.167.29.89 attackbots
B: Magento admin pass /admin/ test (wrong country)
2019-10-28 19:27:52
119.27.189.46 attackspambots
Oct 27 19:25:14 tdfoods sshd\[29720\]: Invalid user password1234 from 119.27.189.46
Oct 27 19:25:14 tdfoods sshd\[29720\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.27.189.46
Oct 27 19:25:16 tdfoods sshd\[29720\]: Failed password for invalid user password1234 from 119.27.189.46 port 39340 ssh2
Oct 27 19:30:28 tdfoods sshd\[30168\]: Invalid user 123456 from 119.27.189.46
Oct 27 19:30:28 tdfoods sshd\[30168\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=119.27.189.46
2019-10-28 19:29:02
141.135.239.180 attackbots
2019-10-22T23:30:21.900784ns525875 sshd\[30695\]: Invalid user dy from 141.135.239.180 port 49982
2019-10-22T23:30:21.906934ns525875 sshd\[30695\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=d8d87efb4.access.telenet.be
2019-10-22T23:30:23.796574ns525875 sshd\[30695\]: Failed password for invalid user dy from 141.135.239.180 port 49982 ssh2
2019-10-22T23:34:34.029101ns525875 sshd\[3383\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=d8d87efb4.access.telenet.be  user=root
2019-10-22T23:45:13.213364ns525875 sshd\[16575\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=d8d87efb4.access.telenet.be  user=root
2019-10-22T23:45:15.226682ns525875 sshd\[16575\]: Failed password for root from 141.135.239.180 port 55098 ssh2
2019-10-22T23:49:26.992281ns525875 sshd\[21698\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhos
...
2019-10-28 19:41:28
103.45.105.236 attackspam
Oct 28 09:37:00 vps sshd[32398]: Failed password for root from 103.45.105.236 port 53124 ssh2
Oct 28 09:54:43 vps sshd[717]: Failed password for root from 103.45.105.236 port 47530 ssh2
...
2019-10-28 19:25:09
46.105.124.52 attackbotsspam
Oct 28 12:47:14 vps01 sshd[17340]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=46.105.124.52
Oct 28 12:47:16 vps01 sshd[17340]: Failed password for invalid user Bash from 46.105.124.52 port 55143 ssh2
2019-10-28 19:48:28
180.169.159.162 attackbots
Oct 28 12:45:04 sso sshd[31668]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=180.169.159.162
Oct 28 12:45:06 sso sshd[31668]: Failed password for invalid user Scooby from 180.169.159.162 port 50376 ssh2
...
2019-10-28 19:52:56
124.163.214.106 attackspambots
Oct 27 23:47:24 ghostname-secure sshd[6473]: Address 124.163.214.106 maps to 106.214.163.124.adsl-pool.sx.cn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 27 23:47:24 ghostname-secure sshd[6473]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=124.163.214.106  user=r.r
Oct 27 23:47:26 ghostname-secure sshd[6473]: Failed password for r.r from 124.163.214.106 port 49763 ssh2
Oct 27 23:47:26 ghostname-secure sshd[6473]: Received disconnect from 124.163.214.106: 11: Bye Bye [preauth]
Oct 27 23:51:48 ghostname-secure sshd[6567]: Address 124.163.214.106 maps to 106.214.163.124.adsl-pool.sx.cn, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!
Oct 27 23:51:50 ghostname-secure sshd[6567]: Failed password for invalid user meg from 124.163.214.106 port 40310 ssh2
Oct 27 23:51:50 ghostname-secure sshd[6567]: Received disconnect from 124.163.214.106: 11: Bye Bye [preauth]
Oct 27 23:55:50 ghos........
-------------------------------
2019-10-28 19:36:14
222.75.167.88 attack
10/28/2019-04:45:02.345804 222.75.167.88 Protocol: 6 ET SCAN Suspicious inbound to MSSQL port 1433
2019-10-28 19:40:11
218.241.243.202 attack
IP Ban Report :  
 https://help-dysk.pl/wordpress-firewall-plugins/ip/218.241.243.202/ 
 
 CN - 1H : (1026)  
 Protection Against DDoS WordPress plugin :  
 "odzyskiwanie danych help-dysk" 
 IP Address Ranges by Country : CN 
 NAME ASN : ASN4847 
 
 IP : 218.241.243.202 
 
 CIDR : 218.241.243.0/24 
 
 PREFIX COUNT : 1024 
 
 UNIQUE IP COUNT : 6630912 
 
 
 ATTACKS DETECTED ASN4847 :  
  1H - 1 
  3H - 1 
  6H - 1 
 12H - 1 
 24H - 4 
 
 DateTime : 2019-10-28 04:45:00 
 
 INFO : Port Scan TELNET Detected and Blocked by ADMIN  - data recovery
2019-10-28 19:38:00
94.23.165.68 attack
Unauthorized connection attempt from IP address 94.23.165.68 on Port 3389(RDP)
2019-10-28 19:35:12

Recently Reported IPs

109.70.193.20 109.70.7.14 109.70.6.177 109.70.2.218
92.237.105.148 109.70.2.101 108.175.15.211 109.71.15.56
109.71.14.194 109.71.194.14 109.71.161.228 109.71.43.54
109.71.72.129 109.71.54.22 109.71.66.174 109.71.72.88
109.72.135.3 109.71.8.40 108.175.150.60 109.72.83.127