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

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

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

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

;; Query time: 43 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sun Feb 23 23:46:46 CST 2020
;; MSG SIZE  rcvd: 116
Host info
34.105.12.74.in-addr.arpa domain name pointer london4745w-lp130-01-74-12-105-34.dsl.bell.ca.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
34.105.12.74.in-addr.arpa	name = london4745w-lp130-01-74-12-105-34.dsl.bell.ca.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
65.49.212.67 attackbotsspam
Oct 15 10:57:53 hanapaa sshd\[439\]: Invalid user sims from 65.49.212.67
Oct 15 10:57:53 hanapaa sshd\[439\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=65.49.212.67.16clouds.com
Oct 15 10:57:55 hanapaa sshd\[439\]: Failed password for invalid user sims from 65.49.212.67 port 45034 ssh2
Oct 15 11:03:30 hanapaa sshd\[1124\]: Invalid user m\&g_2008 from 65.49.212.67
Oct 15 11:03:30 hanapaa sshd\[1124\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=65.49.212.67.16clouds.com
2019-10-16 05:41:52
222.161.177.69 attack
23/tcp
[2019-10-15]1pkt
2019-10-16 05:29:38
112.112.7.202 attackbotsspam
2019-10-15T21:35:42.301455shield sshd\[31309\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.112.7.202  user=root
2019-10-15T21:35:44.447534shield sshd\[31309\]: Failed password for root from 112.112.7.202 port 36714 ssh2
2019-10-15T21:40:49.363097shield sshd\[32401\]: Invalid user @ from 112.112.7.202 port 34372
2019-10-15T21:40:49.369188shield sshd\[32401\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=112.112.7.202
2019-10-15T21:40:51.661774shield sshd\[32401\]: Failed password for invalid user @ from 112.112.7.202 port 34372 ssh2
2019-10-16 05:44:01
114.236.160.62 attackbots
22/tcp
[2019-10-15]1pkt
2019-10-16 05:58:36
139.59.116.30 attackbotsspam
WordPress brute force
2019-10-16 05:40:50
183.196.90.14 attackspambots
(sshd) Failed SSH login from 183.196.90.14 (CN/China/-): 3 in the last 3600 secs; Ports: *; Direction: inout; Trigger: LF_SSHD; Logs: Oct 15 19:42:10 andromeda sshd[32084]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.196.90.14  user=root
Oct 15 19:42:12 andromeda sshd[32084]: Failed password for root from 183.196.90.14 port 56768 ssh2
Oct 15 19:57:20 andromeda sshd[1324]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.196.90.14  user=root
2019-10-16 05:48:20
111.172.104.22 attackbots
Telnet Server BruteForce Attack
2019-10-16 05:22:26
89.120.75.63 attackspam
34567/tcp
[2019-10-15]1pkt
2019-10-16 05:32:50
182.75.248.254 attackspam
Oct 16 00:42:26 pkdns2 sshd\[52416\]: Address 182.75.248.254 maps to nsg-static-254.248.75.182-airtel.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Oct 16 00:42:26 pkdns2 sshd\[52416\]: Invalid user xp from 182.75.248.254Oct 16 00:42:28 pkdns2 sshd\[52416\]: Failed password for invalid user xp from 182.75.248.254 port 36570 ssh2Oct 16 00:46:30 pkdns2 sshd\[52609\]: Address 182.75.248.254 maps to nsg-static-254.248.75.182-airtel.com, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT!Oct 16 00:46:30 pkdns2 sshd\[52609\]: Invalid user pi from 182.75.248.254Oct 16 00:46:32 pkdns2 sshd\[52609\]: Failed password for invalid user pi from 182.75.248.254 port 45938 ssh2
...
2019-10-16 05:53:16
185.216.140.180 attackspam
10/15/2019-23:45:55.888254 185.216.140.180 Protocol: 6 ET SCAN Suspicious inbound to mySQL port 3306
2019-10-16 06:00:58
72.185.233.144 attackbotsspam
Automatic report - Port Scan Attack
2019-10-16 05:47:51
81.190.192.235 attack
Invalid user ubnt from 81.190.192.235 port 52875
2019-10-16 05:31:03
77.42.117.149 attackbots
Automatic report - Port Scan Attack
2019-10-16 05:33:07
139.255.16.162 attack
postfix (unknown user, SPF fail or relay access denied)
2019-10-16 05:38:48
185.202.172.113 attackbots
F2B jail: sshd. Time: 2019-10-15 23:42:20, Reported by: VKReport
2019-10-16 05:49:57

Recently Reported IPs

184.227.174.231 104.168.142.227 212.248.149.116 17.55.166.17
164.41.209.92 39.201.91.45 161.244.121.10 207.145.234.204
216.72.233.202 243.47.188.26 178.217.199.68 89.185.25.4
109.180.251.100 164.172.50.225 122.139.175.99 122.5.236.196
144.3.18.141 120.201.27.92 33.44.80.118 58.62.221.154