City: unknown
Region: unknown
Country: United States
Internet Service Provider: unknown
Hostname: unknown
Organization: unknown
Usage Type: unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 104.16.3.134
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 43947
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;104.16.3.134. IN A
;; AUTHORITY SECTION:
. 398 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2022040301 1800 900 604800 86400
;; Query time: 66 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Apr 04 13:59:07 CST 2022
;; MSG SIZE rcvd: 105Host 134.3.16.104.in-addr.arpa. not found: 3(NXDOMAIN)Server: 183.60.83.19
Address: 183.60.83.19#53
** server can't find 134.3.16.104.in-addr.arpa: NXDOMAIN| IP | Type | Details | Datetime |
|---|---|---|---|
| 221.132.17.74 | attack | $f2bV_matches |
2020-03-04 23:59:35 |
| 92.118.38.42 | attackspam | 2020-03-04 17:58:52 dovecot_login authenticator failed for \(User\) \[92.118.38.42\]: 535 Incorrect authentication data \(set_id=canerkal@org.ua\)2020-03-04 17:59:16 dovecot_login authenticator failed for \(User\) \[92.118.38.42\]: 535 Incorrect authentication data \(set_id=canhete@org.ua\)2020-03-04 17:59:39 dovecot_login authenticator failed for \(User\) \[92.118.38.42\]: 535 Incorrect authentication data \(set_id=canna@org.ua\) ... |
2020-03-05 00:03:14 |
| 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 |
| 222.186.31.166 | attackbotsspam | 2020-03-04T09:15:17.178286homeassistant sshd[23609]: Failed password for root from 222.186.31.166 port 35580 ssh2 2020-03-04T15:54:22.854753homeassistant sshd[2515]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=222.186.31.166 user=root ... |
2020-03-04 23:57:10 |
| 41.60.239.82 | attackbotsspam | 8080/tcp [2020-03-04]1pkt |
2020-03-05 00:04:57 |
| 221.124.17.233 | attackbots | $f2bV_matches |
2020-03-05 00:10:52 |
| 122.51.221.184 | attackbotsspam | Mar 4 09:46:51 plusreed sshd[7290]: Invalid user pengjunyu from 122.51.221.184 ... |
2020-03-05 00:21:45 |
| 58.225.75.147 | attack | " " |
2020-03-05 00:13:06 |
| 107.22.140.114 | attack | 9200/tcp [2020-03-04]1pkt |
2020-03-05 00:35:05 |
| 98.116.57.97 | attack | 81/tcp [2020-03-04]1pkt |
2020-03-05 00:42:09 |
| 115.51.110.252 | attackbotsspam | 23/tcp [2020-03-04]1pkt |
2020-03-05 00:02:05 |
| 183.62.138.52 | attack | Mar 4 16:12:58 localhost sshd\[21989\]: Invalid user spark from 183.62.138.52 port 37575 Mar 4 16:12:58 localhost sshd\[21989\]: pam_unix\(sshd:auth\): authentication failure\; logname= uid=0 euid=0 tty=ssh ruser= rhost=183.62.138.52 Mar 4 16:13:01 localhost sshd\[21989\]: Failed password for invalid user spark from 183.62.138.52 port 37575 ssh2 |
2020-03-05 00:41:47 |
| 221.122.92.59 | attack | $f2bV_matches |
2020-03-05 00:18:31 |
| 116.48.110.190 | attackspambots | Honeypot attack, port: 5555, PTR: n11648110190.netvigator.com. |
2020-03-05 00:10:01 |
| 221.12.137.6 | attackspam | $f2bV_matches |
2020-03-05 00:35:39 |