City: Pretoria
Region: Gauteng
Country: South Africa
Internet Service Provider: unknown
Hostname: unknown
Organization: Triponza
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 197.231.199.30
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63795
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;197.231.199.30. IN A
;; AUTHORITY SECTION:
. 3600 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019061702 1800 900 604800 86400
;; Query time: 2 msec
;; SERVER: 67.207.67.2#53(67.207.67.2)
;; WHEN: Tue Jun 18 17:57:40 CST 2019
;; MSG SIZE rcvd: 118Host 30.199.231.197.in-addr.arpa. not found: 3(NXDOMAIN)
Server: 67.207.67.2
Address: 67.207.67.2#53
** server can't find 30.199.231.197.in-addr.arpa: NXDOMAIN
| IP | Type | Details | Datetime |
|---|---|---|---|
| 221.140.151.235 | attack | $f2bV_matches |
2020-03-04 23:45:12 |
| 192.241.205.120 | attack | Fail2Ban Ban Triggered |
2020-03-04 23:35:51 |
| 197.54.175.170 | attackbotsspam | 1583328975 - 03/04/2020 14:36:15 Host: 197.54.175.170/197.54.175.170 Port: 445 TCP Blocked |
2020-03-04 23:44:19 |
| 23.83.179.208 | attackspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found drjenniferbrandon.com after doing a quick search – you showed up near the top of the rankings, so whatever you’re doing for SEO, looks like it’s working well. So here’s my question – what happens AFTER someone lands on your site? Anything? Research tells us at least 70% of the people who find your site, after a quick once-over, they disappear… forever. That means that all the work and effort you put into getting them to show up, goes down the tubes. Why would you want all that good work – and the great site you’ve built – go to waste? Because the odds are they’ll just skip over calling or even grabbing their phone, leaving you high and dry. But here’s a thought… what if you could make it super-simple for someone to raise their hand, say, “okay, let’s talk” without requiring them to even pull their cell phone from their pocket? You can – thanks to revolutionary new software t |
2020-03-04 23:40:59 |
| 54.38.129.15 | attackbotsspam | 3389/tcp [2020-03-04]1pkt |
2020-03-04 23:43:00 |
| 111.231.89.162 | attack | Mar 4 15:39:58 sso sshd[30977]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.231.89.162 Mar 4 15:40:00 sso sshd[30977]: Failed password for invalid user craig from 111.231.89.162 port 38134 ssh2 ... |
2020-03-04 23:33:02 |
| 178.176.30.211 | attack | $f2bV_matches |
2020-03-04 23:19:31 |
| 221.150.22.201 | attackspam | $f2bV_matches |
2020-03-04 23:31:22 |
| 66.65.120.57 | attackspambots | Brute-force attempt banned |
2020-03-04 23:13:01 |
| 162.216.214.90 | attackbots | 5555/tcp [2020-03-04]1pkt |
2020-03-04 23:48:34 |
| 178.129.127.79 | attackspambots | 445/tcp [2020-03-04]1pkt |
2020-03-04 23:22:25 |
| 212.129.249.202 | attackbots | SSH Brute Force |
2020-03-04 23:11:37 |
| 134.209.18.220 | attackbots | Mar 4 15:51:43 ns381471 sshd[26491]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=134.209.18.220 Mar 4 15:51:45 ns381471 sshd[26491]: Failed password for invalid user ec2-user from 134.209.18.220 port 49866 ssh2 |
2020-03-04 23:23:33 |
| 138.97.216.28 | attackbotsspam | Mar 4 15:55:00 vps647732 sshd[4723]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=138.97.216.28 Mar 4 15:55:02 vps647732 sshd[4723]: Failed password for invalid user rafli from 138.97.216.28 port 52200 ssh2 ... |
2020-03-04 23:14:55 |
| 80.47.50.1 | attackbotsspam | 81/tcp [2020-03-04]1pkt |
2020-03-04 23:37:31 |