广告
提示
工具简介
amrcloud.cn通过本站DNS查询可进行实时DNS检测,能够迅速检测出在不同地区以及不同网络下对域名解析的结果,检测DNS解析是否遭受污染,查看域名污染在全国的分布状况,还能对域名的A记录、CNAME记录、MX记录、NS记录予以查询。
DNS查询结果amrcloud.cn2026-09-03 02:03:22
预估消耗 0 检测点,实际消耗以【检测点账单】为准
30

检测节点

响应时间分布 域名污染分布

污染比例:0%

登录51CESU,立即查看域名污染全国分布情况
立即登录
概览 被污染 (0) 状态码4XX (0) 客户端请求错误(请求的资源不存在、权限不足等) 状态码5XX (0) 服务器故障,处理请求时内部出错无法访问 响应超时 (0)
区域/运营商 响应最快 响应最慢 平均响应
全部 浙江杭州移动18ms 北京移动395ms 83.033ms
电信 -23ms 浙江温州电信98ms 59.182ms
移动 浙江杭州移动18ms 北京移动395ms 85.5ms
联通 -53ms 北京联通260ms 116.286ms
华东 浙江杭州移动18ms 浙江温州联通131ms 59.571ms
华北 -23ms 北京移动395ms 180.5ms
华南 -59ms -95ms 83ms
华中 -33ms -33ms 33ms
西北 -47ms 新疆博尔塔拉蒙古自治州联通117ms 77.833ms
西南 四川广安电信68ms -112ms 79ms
东北 -36ms -53ms 41.667ms
解析占比
全部 电信 移动 联通 被污染
8.136.98.168
8.136.98.168
DNS查询详情
全部
响应超时 被污染
节点数:/
检测点
运营商 检测节点

解析时间

解析内容 操作
电信 青海
63ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 63 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 419

详情
详情 HTTP PING DNS
电信 西藏
74ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 74 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
电信 海南
59ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 59 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 419

详情
详情 HTTP PING DNS
电信 贵州
72ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 72 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
电信 北京
23ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 23 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
电信 云南
69ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		3600	IN	A	8.136.98.168
;; Query time: 69 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 56

详情
详情 HTTP PING DNS
电信 宁夏
51ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 51 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
电信 江西宜春
37ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	600	IN	A	8.136.98.168

;; Query time: 37 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
电信 上海
37ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	606	IN	A	8.136.98.168

;; Query time: 37 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
电信 四川广安
68ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 68 msec
;; SERVER: 223.5.5.5#53(223.5.5.5) (UDP)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56

详情
详情 HTTP PING DNS
电信 浙江温州
98ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	600	IN	A	8.136.98.168

;; Query time: 98 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
移动 黑龙江
36ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 36 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 419

详情
详情 HTTP PING DNS
移动 湖南
33ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 33 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
移动 上海
51ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 51 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
移动 海南
95ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 95 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 419

详情
详情 HTTP PING DNS
移动 青海
47ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 47 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 56

详情
详情 HTTP PING DNS
移动 云南
112ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 112 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
移动 北京
395ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	300	IN	A	8.136.98.168

;; Query time: 395 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Sep 03 02:02:17 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
移动 甘肃庆阳
114ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	600	IN	A	8.136.98.168

;; Query time: 114 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
移动 河北唐山
44ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	600	IN	A	8.136.98.168

;; Query time: 44 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
移动 辽宁大连
36ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 36 msec
;; SERVER: 127.0.0.1#53(127.0.0.1) (UDP)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
移动 山东青岛
45ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	600	IN	A	8.136.98.168

;; Query time: 45 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
移动 浙江杭州
18ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	600	IN	A	8.136.98.168

;; Query time: 18 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
联通 广西
91ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 91 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
联通 海南
87ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 87 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
联通 吉林
53ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 53 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Sep 02 18:02:17 UTC 2026
;; MSG SIZE  rcvd: 45

详情
详情 HTTP PING DNS
联通 北京
260ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 260 msec
;; SERVER: 8.8.8.8#53(8.8.8.8) (UDP)
;; WHEN: Thu Sep 03 02:02:17 CST 2026
;; MSG SIZE  rcvd: 56

详情
详情 HTTP PING DNS
联通 甘肃庆阳
75ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	600	IN	A	8.136.98.168

;; Query time: 75 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS
联通 新疆博尔塔拉蒙古自治州
117ms 8.136.98.168[浙江杭州阿里云]
amrcloud.cn.		600	IN	A	8.136.98.168
;; Query time: 117 msec
;; SERVER: 119.29.29.29#53(119.29.29.29) (UDP)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 68

详情
详情 HTTP PING DNS
联通 浙江温州
131ms 8.136.98.168[浙江杭州阿里云]
; <<>> DiG Go <<>> +noall +answer +stats amrcloud.cn
;; global options: +cmd

;; ANSWER SECTION:
amrcloud.cn.	600	IN	A	8.136.98.168

;; Query time: 131 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Thu Sep 03 02:02:16 CST 2026
;; MSG SIZE  rcvd: 56
详情
详情 HTTP PING DNS

查询结果仅供参考,不保证100%准确。

amrcloud.cn 优化建议

1、使用在线DNS测速工具定期监测不同地区解析响应情况,重点关注响应较慢的区域,分析是否存在网络链路问题。
2、结合DNS解析速度测试结果,优化解析配置,选择解析速度更稳定的服务器,减少因解析延迟导致的用户访问等待。
3、通过DNS污染检测工具检查是否存在解析异常,确保域名解析指向正确的服务器地址,避免用户访问受阻。

其他工具历史

更新时间 2026-09-03 13:03:02
广告
广告