City: De Kwakel
Region: North Holland
Country: Netherlands
Internet Service Provider: KPN
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 188.204.15.218
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12027
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;188.204.15.218. IN A
;; AUTHORITY SECTION:
. 338 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2020030801 1800 900 604800 86400
;; Query time: 108 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Mar 09 05:55:46 CST 2020
;; MSG SIZE rcvd: 118218.15.204.188.in-addr.arpa domain name pointer static.kpn.net.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
218.15.204.188.in-addr.arpa name = static.kpn.net.
Authoritative answers can be found from:| IP | Type | Details | Datetime |
|---|---|---|---|
| 198.20.180.70 | attack | (From cath@send.kathreadwrites.net) Hello I wanted to share a quick ranking case study with you (I'm a copywriter and onpage SEO expert). 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:48:26 |
| 128.199.162.2 | attack | SSH Brute-Force reported by Fail2Ban |
2019-07-23 05:12:40 |
| 183.150.166.21 | attack | [portscan] Port scan |
2019-07-23 05:21:34 |
| 37.49.224.150 | attackspam | firewall-block, port(s): 81/tcp |
2019-07-23 05:34:11 |
| 189.5.176.21 | attackbots | Jul 22 14:42:07 mxgate1 postfix/postscreen[7227]: CONNECT from [189.5.176.21]:11294 to [176.31.12.44]:25 Jul 22 14:42:07 mxgate1 postfix/dnsblog[7436]: addr 189.5.176.21 listed by domain cbl.abuseat.org as 127.0.0.2 Jul 22 14:42:07 mxgate1 postfix/dnsblog[7229]: addr 189.5.176.21 listed by domain zen.spamhaus.org as 127.0.0.11 Jul 22 14:42:07 mxgate1 postfix/dnsblog[7229]: addr 189.5.176.21 listed by domain zen.spamhaus.org as 127.0.0.4 Jul 22 14:42:07 mxgate1 postfix/dnsblog[7228]: addr 189.5.176.21 listed by domain ix.dnsbl.xxxxxx.net as 127.0.0.2 Jul 22 14:42:13 mxgate1 postfix/postscreen[7227]: DNSBL rank 4 for [189.5.176.21]:11294 Jul x@x ........ ----------------------------------------------- https://www.blocklist.de/en/view.html?ip=189.5.176.21 |
2019-07-23 04:58:57 |
| 209.97.153.35 | attack | Automatic report - Banned IP Access |
2019-07-23 05:07:40 |
| 123.24.113.118 | attack | Jul 22 15:11:24 ks10 sshd[9493]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=123.24.113.118 Jul 22 15:11:27 ks10 sshd[9493]: Failed password for invalid user admin from 123.24.113.118 port 37275 ssh2 ... |
2019-07-23 05:36:17 |
| 186.145.62.187 | attackspam | Spam Timestamp : 22-Jul-19 13:32 _ BlockList Provider combined abuse _ (679) |
2019-07-23 04:50:46 |
| 185.220.101.66 | attackspambots | Mon, 22 Jul 2019 20:48:05 +0000 likely compromised host or open proxy. ddos rate spidering |
2019-07-23 05:25:16 |
| 95.38.212.11 | attack | Automatic report - Port Scan Attack |
2019-07-23 05:28:12 |
| 203.172.161.11 | attackspambots | Jul 22 23:05:44 v22019058497090703 sshd[5184]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.172.161.11 Jul 22 23:05:47 v22019058497090703 sshd[5184]: Failed password for invalid user brady from 203.172.161.11 port 57308 ssh2 Jul 22 23:11:27 v22019058497090703 sshd[5590]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=203.172.161.11 ... |
2019-07-23 05:22:44 |
| 85.154.207.23 | attack | Automatic report - Port Scan Attack |
2019-07-23 04:54:30 |
| 200.52.36.61 | attack | Automatic report - Port Scan Attack |
2019-07-23 04:47:56 |
| 190.13.129.34 | attackbots | Invalid user zope from 190.13.129.34 port 50220 |
2019-07-23 05:19:29 |
| 183.150.138.129 | attack | firewall-block, port(s): 23/tcp |
2019-07-23 05:12:19 |