城市(city): unknown
省份(region): unknown
国家(country): United States
运营商(isp): unknown
主机名(hostname): unknown
机构(organization): unknown
使用类型(Usage Type): unknown
b; <<>> DiG 9.10.3-P4-Ubuntu <<>> 70.63.130.75
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 40659
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;70.63.130.75. IN A
;; AUTHORITY SECTION:
. 237 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019122900 1800 900 604800 86400
;; Query time: 111 msec
;; SERVER: 183.60.83.19#53(183.60.83.19)
;; WHEN: Mon Dec 30 00:22:37 CST 2019
;; MSG SIZE rcvd: 11675.130.63.70.in-addr.arpa domain name pointer rrcs-70-63-130-75.midsouth.biz.rr.com.Server: 183.60.83.19
Address: 183.60.83.19#53
Non-authoritative answer:
75.130.63.70.in-addr.arpa name = rrcs-70-63-130-75.midsouth.biz.rr.com.
Authoritative answers can be found from:| IP | 类型 | 评论内容 | 时间 |
|---|---|---|---|
| 23.95.204.95 | attackspambots | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mcfaddenchiropractic.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 softwar |
2020-08-11 05:26:07 |
| 42.200.66.164 | attackspam | Aug 10 20:31:31 IngegnereFirenze sshd[1146]: User root from 42.200.66.164 not allowed because not listed in AllowUsers ... |
2020-08-11 05:15:07 |
| 49.235.46.16 | attackspambots | 2020-08-10T20:26:47.042650abusebot-2.cloudsearch.cf sshd[30736]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.46.16 user=root 2020-08-10T20:26:49.752427abusebot-2.cloudsearch.cf sshd[30736]: Failed password for root from 49.235.46.16 port 45554 ssh2 2020-08-10T20:30:00.517894abusebot-2.cloudsearch.cf sshd[30743]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.46.16 user=root 2020-08-10T20:30:02.389501abusebot-2.cloudsearch.cf sshd[30743]: Failed password for root from 49.235.46.16 port 54364 ssh2 2020-08-10T20:33:17.868192abusebot-2.cloudsearch.cf sshd[30755]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=49.235.46.16 user=root 2020-08-10T20:33:20.116200abusebot-2.cloudsearch.cf sshd[30755]: Failed password for root from 49.235.46.16 port 34946 ssh2 2020-08-10T20:36:32.103818abusebot-2.cloudsearch.cf sshd[30762]: pam_unix(sshd:auth): authenticat ... |
2020-08-11 05:06:39 |
| 117.193.79.162 | attackspam | Aug 10 21:43:12 gospond sshd[21353]: Failed password for root from 117.193.79.162 port 43342 ssh2 Aug 10 21:43:10 gospond sshd[21353]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=117.193.79.162 user=root Aug 10 21:43:12 gospond sshd[21353]: Failed password for root from 117.193.79.162 port 43342 ssh2 ... |
2020-08-11 05:05:43 |
| 141.98.10.195 | attackbotsspam | Automatic report - Banned IP Access |
2020-08-11 05:17:21 |
| 23.95.97.227 | attackbotsspam | (From eric@talkwithwebvisitor.com) Hey there, I just found your site, quick question… My name’s Eric, I found mcfaddenchiropractic.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 softwar |
2020-08-11 05:18:05 |
| 175.125.94.166 | attackspam | Aug 10 17:01:14 ny01 sshd[29469]: Failed password for root from 175.125.94.166 port 50486 ssh2 Aug 10 17:04:29 ny01 sshd[29869]: Failed password for root from 175.125.94.166 port 41256 ssh2 |
2020-08-11 05:12:50 |
| 200.29.112.68 | attackspambots | Unauthorized connection attempt from IP address 200.29.112.68 on Port 445(SMB) |
2020-08-11 05:30:19 |
| 192.200.215.91 | attackbotsspam | WordPress vulnerability sniffing (looking for /wp-content/plugins/videowhisper-video-presentation/vp/translation.php) |
2020-08-11 05:31:19 |
| 111.249.105.128 | attack | Unauthorized connection attempt from IP address 111.249.105.128 on Port 445(SMB) |
2020-08-11 05:21:51 |
| 185.98.227.1 | attack | Unauthorized connection attempt from IP address 185.98.227.1 on Port 445(SMB) |
2020-08-11 05:24:33 |
| 222.124.202.179 | attackbotsspam | Unauthorized connection attempt from IP address 222.124.202.179 on Port 445(SMB) |
2020-08-11 05:11:46 |
| 87.118.116.103 | attackspambots | Automatic report - Banned IP Access |
2020-08-11 05:13:21 |
| 31.43.31.64 | attack | Unauthorized connection attempt from IP address 31.43.31.64 on Port 445(SMB) |
2020-08-11 05:17:02 |
| 218.92.0.216 | attackspam | Aug 10 23:06:49 * sshd[4010]: Failed password for root from 218.92.0.216 port 33172 ssh2 |
2020-08-11 05:10:59 |