`beijingguide2008.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::ac43:9649^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3036::6815:5818^{🇺🇸 Cloudflare2606:4700:3036::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.88.24^{Cloudflare104.21.80.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.150.73^{🇺🇸 Cloudflare172.67.144.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`jo.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3aac^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jo.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0ac^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`jo.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20ac^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`jo.ns.cloudflare.com`
		A	108.162.192.172^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jo.ns.cloudflare.com`
		A	172.64.32.172^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jo.ns.cloudflare.com`
		A	173.245.58.172^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`jo.ns.cloudflare.com`
NS	`zeus.ns.cloudflare.com`
		A	2606:4700:58::adf5:3bf9^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zeus.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c1f9^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`zeus.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:21f9^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`zeus.ns.cloudflare.com`
		A	108.162.193.249^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zeus.ns.cloudflare.com`
		A	172.64.33.249^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zeus.ns.cloudflare.com`
		A	173.245.59.249^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zeus.ns.cloudflare.com`
MX	`route1.mx.cloudflare.net` ⭐
		A	2606:4700:f5::b^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::c^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	2606:4700:f5::d^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.11^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.12^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
		A	162.159.205.13^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route1.mx.cloudflare.net`
MX	`route3.mx.cloudflare.net`⁽⁷⁹⁾
		A	2606:4700:f5::11^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::12^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	2606:4700:f5::13^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.23^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.24^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
		A	162.159.205.25^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route3.mx.cloudflare.net`
MX	`route2.mx.cloudflare.net`⁽⁹⁸⁾
		A	2606:4700:f5::e^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::f^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	2606:4700:f5::10^{🇺🇸 Cloudflare2606:4700:f5::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.17^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.18^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
		A	162.159.205.19^{Cloudflare162.159.205.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`route2.mx.cloudflare.net`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.88.24, 172.67.150.73
		IPv6 hints	2606:4700:3033::ac43:9649, 2606:4700:3036::6815:5818
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=158, name=cloudflare-ech.com
SOA	`jo.ns.cloudflare.com`dns@cloudflare.com serial=2399723841

`com`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.gtld-servers.net` ⭐
	NS	`b.gtld-servers.net`
	NS	`c.gtld-servers.net`
	NS	`d.gtld-servers.net`
	NS	`e.gtld-servers.net`
	NS	`f.gtld-servers.net`
	NS	`g.gtld-servers.net`
	NS	`h.gtld-servers.net`
	NS	`i.gtld-servers.net`
	NS	`j.gtld-servers.net`
	NS	`k.gtld-servers.net`
	NS	`l.gtld-servers.net`
	NS	`m.gtld-servers.net`
	SOA	`a.gtld-servers.net`nstld@verisign-grs.com serial=1776266562

WOT: NOT_SAFE (60/100)

Previously MX for

beijingguide2008.com

Same first word

beijingguide2008.com

DNS History

22 records (9 active, 13 former)

●NSjo.ns.cloudflare.com2026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

○NSns23.domaincontrol.com2015-11-13 → 2015-11-13 · 3 obs

● 2015-11-13 22:01:54
○ 2016-02-27 21:09:36
○ 2026-04-15 15:25:14

○NSns24.domaincontrol.com2015-11-13 → 2015-11-13 · 3 obs

● 2015-11-13 22:01:54
○ 2016-02-27 21:09:36
○ 2026-04-15 15:25:14

○NSns67a.turnkeywebspace.com2016-02-27 → 2016-07-01 · 5 obs

○ 2015-11-13 22:01:54
● 2016-02-27 21:09:36
● 2016-07-01 13:08:06
○ 2017-02-13 22:00:26
○ 2026-04-15 15:25:14

○NSns67b.turnkeywebspace.com2016-02-27 → 2016-07-01 · 5 obs

○ 2015-11-13 22:01:54
● 2016-02-27 21:09:36
● 2016-07-01 13:08:06
○ 2017-02-13 22:00:26
○ 2026-04-15 15:25:14

○NSns84a.turnkeywebspace.net2017-02-13 → 2017-02-13 · 4 obs

○ 2016-07-01 13:08:06
● 2017-02-13 22:00:26
○ 2019-12-24 02:16:50
○ 2026-04-15 15:25:14

○NSns84b.turnkeywebspace.net2017-02-13 → 2017-02-13 · 4 obs

○ 2016-07-01 13:08:06
● 2017-02-13 22:00:26
○ 2019-12-24 02:16:50
○ 2026-04-15 15:25:14

●NSzeus.ns.cloudflare.com2026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

○MXbeijingguide2008.com2016-02-27 → 2017-02-13 · 5 obs

○ 2015-11-13 22:01:54
● 2016-02-27 21:09:36
● 2017-02-13 22:00:26
○ 2019-12-24 02:16:50
○ 2026-04-15 15:25:14

○MXmailstore1.secureserver.net2015-11-13 → 2015-11-13 · 3 obs

● 2015-11-13 22:01:54
○ 2016-02-27 21:09:36
○ 2026-04-15 15:25:14

●MXroute1.mx.cloudflare.net2026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

●MXroute2.mx.cloudflare.net2026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

●MXroute3.mx.cloudflare.net2026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

○MXsmtp.secureserver.net2015-11-13 → 2015-11-13 · 3 obs

● 2015-11-13 22:01:54
○ 2016-02-27 21:09:36
○ 2026-04-15 15:25:14

●A104.21.88.242026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

●A172.67.150.732026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

○A173.198.217.1352017-02-13 → 2017-02-13 · 4 obs

○ 2016-07-01 13:08:06
● 2017-02-13 22:00:26
○ 2019-12-24 02:16:50
○ 2026-04-15 15:25:14

○A2604:7c00:1a:8::10d2016-02-27 → 2017-02-13 · 5 obs

○ 2015-11-13 22:01:54
● 2016-02-27 21:09:36
● 2017-02-13 22:00:26
○ 2019-12-24 02:16:50
○ 2026-04-15 15:25:14

●A2606:4700:3033::ac43:96492026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

●A2606:4700:3036::6815:58182026-04-14 → 2026-04-15 · 3 obs

○ 2019-12-24 02:16:50
● 2026-04-14 11:07:34
● 2026-04-15 15:25:14

○A50.63.202.522015-11-13 → 2015-11-13 · 3 obs

● 2015-11-13 22:01:54
○ 2016-02-27 21:09:36
○ 2026-04-15 15:25:14

○A66.206.42.612016-02-27 → 2016-07-01 · 5 obs

○ 2015-11-13 22:01:54
● 2016-02-27 21:09:36
● 2016-07-01 13:08:06
○ 2017-02-13 22:00:26
○ 2026-04-15 15:25:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, j.gtld-servers.net...	-
beijingguide2008.com	jo.ns.cloudflare.com, zeus.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.192.172

NS records: jo.ns.cloudflare.com, zeus.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for beijingguide2008.com (unsigned zone)

⏱️ Timing

Total: 274ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`104.21.88.24, 172.67.150.73`
AAAA	2	`2606:4700:3033::ac43:9649, 2606:4700:3036::6815:5818`
NS	2	`jo.ns.cloudflare.com, zeus.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 43), route3.mx.cloudflare.net (pri: 79)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`jo.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (jo.ns.cloudflare.com, jo.ns.cloudflare.com, jo.ns.cloudflare.com...)

Analysis

IP Addresses

beijingguide2008.com maps to four IP numbers: 2606:4700:3033::ac43:9649, 2606:4700:3036::6815:5818, 104.21.88.24 and 172.67.150.73.

Other host names, for instance pao.gr, liquidcreativity.com, lusaschool.com, playboyph.com and 95oj1.xinwenw.cc share IP numbers with beijingguide2008.com.

Name Servers

Two name servers jo.ns.cloudflare.com and zeus.ns.cloudflare.com handle delegation for beijingguide2008.com.

beijingguide2008.com uses the same name server setup as other domains, for example alohihawaii.com, koktips.se, ddsos.org, overload.cl and clasmo-kyoto.jp.

beijingguide2008.com partially shares name servers with other domains; examples include bazaaranatolia.com, newblack.co.uk, id.discount, buyl2m.com and 60touch.com.

These name servers are commonly used with logan.ns.cloudflare.com, ivan.ns.cloudflare.com and megan.ns.cloudflare.com.

Host names with six IP numbers: jo.ns.cloudflare.com points to: 2606:4700:50::adf5:3aac, 2803:f800:50::6ca2:c0ac, 2a06:98c1:50::ac40:20ac, 108.162.192.172, 172.64.32.172 and 173.245.58.172; zeus.ns.cloudflare.com points to: 2606:4700:58::adf5:3bf9, 2803:f800:50::6ca2:c1f9, 2a06:98c1:50::ac40:21f9, 108.162.193.249, 172.64.33.249 and 173.245.59.249.

Mail Servers

beijingguide2008.com is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

beijingguide2008.com shares some mail servers with other domains, at least partially, such as callver.com, bitcoinhk.com, gstsc.net, 100fails.com and pinkpeonyphotography.com.

Host names with six IP numbers:

route1.mx.cloudflare.net points to 2606:4700:f5::b, 2606:4700:f5::c, 2606:4700:f5::d, 162.159.205.11, 162.159.205.12 and 162.159.205.13.

route2.mx.cloudflare.net points to 2606:4700:f5::e, 2606:4700:f5::f, 2606:4700:f5::10, 162.159.205.17, 162.159.205.18 and 162.159.205.19.

route3.mx.cloudflare.net points to 2606:4700:f5::11, 2606:4700:f5::12, 2606:4700:f5::13, 162.159.205.23, 162.159.205.24 and 162.159.205.25.

beijingguide2008.com - robtex.com