City: unknown
Region: unknown
Country: Multicast Address
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 229.140.159.133
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37148
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;229.140.159.133. IN A
;; AUTHORITY SECTION:
. 30 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2025030800 1800 900 604800 86400
;; Query time: 17 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Sat Mar 08 23:06:57 CST 2025
;; MSG SIZE rcvd: 108Host 133.159.140.229.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 133.159.140.229.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 64.94.208.204 | attack | (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-05 00:03:40 |
| 42.98.175.217 | attack | Honeypot attack, port: 5555, PTR: 42-98-175-217.static.netvigator.com. |
2020-03-05 00:40:35 |
| 189.15.38.74 | attackbotsspam | 23/tcp [2020-03-04]1pkt |
2020-03-05 00:18:56 |
| 42.118.71.189 | attackbots | 23/tcp 23/tcp 23/tcp... [2020-03-04]6pkt,1pt.(tcp) |
2020-03-05 00:22:41 |
| 221.120.217.18 | attackspam | $f2bV_matches |
2020-03-05 00:28:58 |
| 103.249.237.117 | attack | 445/tcp [2020-03-04]1pkt |
2020-03-05 00:39:09 |
| 218.92.0.171 | attackspam | Mar 4 16:45:53 combo sshd[18916]: Failed password for root from 218.92.0.171 port 63712 ssh2 Mar 4 16:45:57 combo sshd[18916]: Failed password for root from 218.92.0.171 port 63712 ssh2 Mar 4 16:46:00 combo sshd[18916]: Failed password for root from 218.92.0.171 port 63712 ssh2 ... |
2020-03-05 00:49:26 |
| 110.54.250.99 | attackbots | 445/tcp [2020-03-04]1pkt |
2020-03-05 00:17:35 |
| 41.60.239.82 | attackbotsspam | 8080/tcp [2020-03-04]1pkt |
2020-03-05 00:04:57 |
| 41.208.70.187 | attackbotsspam | Honeypot attack, port: 445, PTR: 41.208.70.187.static.ltt.ly. |
2020-03-05 00:34:13 |
| 58.225.75.147 | attack | " " |
2020-03-05 00:13:06 |
| 200.41.98.6 | attackbots | Honeypot attack, port: 445, PTR: PTR record not found |
2020-03-05 00:20:44 |
| 113.172.212.176 | attackspambots | suspicious action Wed, 04 Mar 2020 10:36:04 -0300 |
2020-03-05 00:10:27 |
| 221.122.67.66 | attack | $f2bV_matches |
2020-03-05 00:23:07 |
| 81.255.10.137 | attackspam | Invalid user apache from 81.255.10.137 port 34558 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.255.10.137 Failed password for invalid user apache from 81.255.10.137 port 34558 ssh2 Invalid user ftp from 81.255.10.137 port 50942 pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=81.255.10.137 |
2020-03-05 00:43:06 |