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

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

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

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

;; Query time: 0 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Tue Jun 11 14:55:52 CST 2019
;; MSG SIZE  rcvd: 118

Host info
Host 212.149.69.129.in-addr.arpa. not found: 3(NXDOMAIN)
Nslookup info:
Server:		67.207.67.2
Address:	67.207.67.2#53

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

Related IP info:
Related comments:
IP Type Details Datetime
177.106.151.64 attack
Port Scan
2019-12-12 17:49:44
178.128.21.38 attackbots
Dec 12 09:50:17 web8 sshd\[3006\]: Invalid user kernel123 from 178.128.21.38
Dec 12 09:50:17 web8 sshd\[3006\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.21.38
Dec 12 09:50:19 web8 sshd\[3006\]: Failed password for invalid user kernel123 from 178.128.21.38 port 36250 ssh2
Dec 12 09:56:45 web8 sshd\[6293\]: Invalid user headache from 178.128.21.38
Dec 12 09:56:45 web8 sshd\[6293\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=178.128.21.38
2019-12-12 18:07:12
103.208.220.132 attackspambots
CVE-2018-7600 SA-CORE-2018-002
2019-12-12 17:32:59
117.240.111.135 attackspambots
Port Scan
2019-12-12 18:07:55
111.230.152.175 attack
$f2bV_matches
2019-12-12 18:03:42
187.32.227.205 attackbotsspam
Automatic report: SSH brute force attempt
2019-12-12 18:08:13
201.16.246.71 attackspam
[Aegis] @ 2019-12-12 07:58:59  0000 -> Attempted Administrator Privilege Gain: ET SCAN LibSSH Based Frequent SSH Connections Likely BruteForce Attack
2019-12-12 17:51:06
106.12.136.62 attackspambots
Dec 12 10:27:04 legacy sshd[28241]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.136.62
Dec 12 10:27:06 legacy sshd[28241]: Failed password for invalid user isaque from 106.12.136.62 port 45858 ssh2
Dec 12 10:34:02 legacy sshd[28538]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=106.12.136.62
...
2019-12-12 18:05:06
68.34.15.8 attackbotsspam
SSH bruteforce
2019-12-12 18:01:58
104.129.4.229 attackspam
(From eric@talkwithcustomer.com) Hello knutsonchiropractic.com,

People ask, “why does TalkWithCustomer work so well?”

It’s simple.

TalkWithCustomer enables you to connect with a prospective customer at EXACTLY the Perfect Time.

- NOT one week, two weeks, three weeks after they’ve checked out your website knutsonchiropractic.com.
- NOT with a form letter style email that looks like it was written by a bot.
- NOT with a robocall that could come at any time out of the blue.

TalkWithCustomer connects you to that person within seconds of THEM asking to hear from YOU.

They kick off the conversation.

They take that first step.

They ask to hear from you regarding what you have to offer and how it can make their life better. 

And it happens almost immediately. In real time. While they’re still looking over your website knutsonchiropractic.com, trying to make up their mind whether you are right for them.

When you connect with them at that very moment it’s the ultimate in Perfect Timing –
2019-12-12 18:03:23
41.214.138.178 attackbots
Brute-force attempt banned
2019-12-12 17:36:19
185.143.223.128 attackbotsspam
Dec 12 13:06:56 debian-2gb-vpn-nbg1-1 kernel: [523596.260664] [UFW BLOCK] IN=eth0 OUT= MAC=96:00:00:38:96:44:d2:74:7f:6e:37:e3:08:00 SRC=185.143.223.128 DST=78.46.192.101 LEN=40 TOS=0x00 PREC=0x00 TTL=245 ID=1144 PROTO=TCP SPT=59481 DPT=10522 WINDOW=1024 RES=0x00 SYN URGP=0
2019-12-12 18:07:34
123.143.11.195 attackspam
3389BruteforceFW22
2019-12-12 17:56:53
41.236.106.45 attackbots
Cluster member 192.168.0.31 (-) said, DENY 41.236.106.45, Reason:[(imapd) Failed IMAP login from 41.236.106.45 (EG/Egypt/host-41.236.106.45.tedata.net): 1 in the last 3600 secs]
2019-12-12 18:10:41
51.68.47.45 attackspam
Dec 12 10:37:07 markkoudstaal sshd[21648]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.47.45
Dec 12 10:37:09 markkoudstaal sshd[21648]: Failed password for invalid user apple from 51.68.47.45 port 37118 ssh2
Dec 12 10:42:23 markkoudstaal sshd[22256]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=51.68.47.45
2019-12-12 17:48:17

Recently Reported IPs

64.180.108.31 139.59.63.15 180.76.15.158 217.182.6.180
184.105.139.90 92.254.153.163 181.52.126.247 162.243.147.15
185.122.104.197 66.65.9.58 188.2.59.218 73.225.156.22
170.111.126.6 80.240.28.245 145.102.6.43 77.53.90.10
114.106.73.225 46.151.7.253 51.79.29.55 103.12.160.129