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

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

;; QUESTION SECTION:
;81.164.18.212.			IN	A

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

;; Query time: 35 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Tue Feb 18 16:30:58 CST 2025
;; MSG SIZE  rcvd: 106
Host info
212.18.164.81.in-addr.arpa domain name pointer d51A412D4.access.telenet.be.
Nslookup info:
Server:		183.60.83.19
Address:	183.60.83.19#53

Non-authoritative answer:
212.18.164.81.in-addr.arpa	name = d51A412D4.access.telenet.be.

Authoritative answers can be found from:
Related IP info:
Related comments:
IP Type Details Datetime
129.45.5.129 attack
Jul 22 15:02:39 mxgate1 postfix/postscreen[7227]: CONNECT from [129.45.5.129]:18406 to [176.31.12.44]:25
Jul 22 15:02:39 mxgate1 postfix/dnsblog[7233]: addr 129.45.5.129 listed by domain zen.spamhaus.org as 127.0.0.4
Jul 22 15:02:39 mxgate1 postfix/dnsblog[7233]: addr 129.45.5.129 listed by domain zen.spamhaus.org as 127.0.0.11
Jul 22 15:02:39 mxgate1 postfix/dnsblog[7797]: addr 129.45.5.129 listed by domain cbl.abuseat.org as 127.0.0.2
Jul 22 15:02:45 mxgate1 postfix/postscreen[7227]: DNSBL rank 3 for [129.45.5.129]:18406
Jul x@x
Jul 22 15:02:46 mxgate1 postfix/postscreen[7227]: HANGUP after 0.29 from [129.45.5.129]:18406 in tests after SMTP handshake
Jul 22 15:02:46 mxgate1 postfix/postscreen[7227]: DISCONNECT [129.45.5.129]:18406


........
-----------------------------------------------
https://www.blocklist.de/en/view.html?ip=129.45.5.129
2019-07-23 05:17:43
51.38.237.214 attackspambots
DATE:2019-07-22 18:28:04, IP:51.38.237.214, PORT:ssh SSH brute force auth (thor)
2019-07-23 04:51:37
128.14.209.226 attackspam
Microsoft Windows HTTP.sys Remote Code Execution Vulnerability
2019-07-23 05:01:31
185.161.252.208 attackbots
[ ?? ] From bounce5@corretora-corretora.com.br Mon Jul 22 10:12:36 2019
 Received: from host4.corretora-corretora.com.br ([185.161.252.208]:46809)
2019-07-23 04:40:22
186.145.62.187 attackspam
Spam Timestamp : 22-Jul-19 13:32 _ BlockList Provider  combined abuse _ (679)
2019-07-23 04:50:46
134.90.149.146 attackbotsspam
Spam-Mail via Contact-Form 22.07.2019 / 20:46
IP-Adresse    | 134.90.149.146
2019-07-23 05:10:57
209.97.153.35 attack
Automatic report - Banned IP Access
2019-07-23 05:07:40
60.189.192.120 attackspambots
2019-07-22T16:49:42.924989abusebot-6.cloudsearch.cf sshd\[29942\]: Invalid user wkidup from 60.189.192.120 port 34387
2019-07-23 04:43:54
128.199.162.2 attack
SSH Brute-Force reported by Fail2Ban
2019-07-23 05:12:40
198.245.72.70 attackbotsspam
(From cath@mail.kathreadwrites.net) Hello

I'm an SEO copywriter & wanted to share a quick ranking case study with you.

Google Loves the RIGHT WORDS in the RIGHT PLACE. I Got It Wrong.

I changed 8 words on a page...and you won't believe what happened.

So I wrote a case study about it.

Read it here: https://kathreadwrites.net/onpage-us/ ?
 
Put the WRONG WORDS in the WRONG PLACE

and you will not rank. PERIOD.

I hope this case study inspires you to check out your own on-page optimization.

Be Amazing

Cath

P.S. To get in touch, please use the contact form on my website instead of emailing me.

Unsubscribe
2019-07-23 04:41:19
187.217.199.20 attackspambots
Jul 22 16:51:17 SilenceServices sshd[23835]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.217.199.20
Jul 22 16:51:19 SilenceServices sshd[23835]: Failed password for invalid user dev from 187.217.199.20 port 47114 ssh2
Jul 22 16:56:26 SilenceServices sshd[29356]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=187.217.199.20
2019-07-23 04:46:00
77.138.145.133 attackspambots
Jul 22 15:52:56 mout sshd[13828]: Invalid user bh from 77.138.145.133 port 60082
Jul 22 15:52:58 mout sshd[13828]: Failed password for invalid user bh from 77.138.145.133 port 60082 ssh2
Jul 22 16:30:38 mout sshd[14848]: Invalid user mariano from 77.138.145.133 port 51102
2019-07-23 04:33:58
196.11.231.220 attackbots
DATE:2019-07-22 19:39:00, IP:196.11.231.220, PORT:ssh brute force auth on SSH service (patata)
2019-07-23 05:11:45
106.12.215.130 attack
ssh failed login
2019-07-23 04:55:46
163.172.160.182 attackbotsspam
port scan and connect, tcp 22 (ssh)
2019-07-23 04:37:18

Recently Reported IPs

98.90.141.255 172.214.87.246 242.104.140.204 157.210.153.62
122.225.66.190 224.82.76.208 235.189.137.209 136.103.2.60
226.102.191.34 78.195.49.237 236.29.195.154 231.232.218.236
135.73.234.18 195.186.123.61 6.219.93.186 87.192.251.36
136.190.164.193 125.205.156.83 6.30.54.235 9.185.180.164