`microsofttoken.com`

DNSSEC	⚠️ Not signed
A	185.53.179.128^{🇩🇪 TEAMINTERNET-AS185.53.179.0/24 Registration for Team Internet by Next Dimension}
NS	`ns1.dyna-ns.net` ⭐
		A	2400:cb00:2049:1::a29f:1a5c^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1b9e^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.92^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
		A	162.159.27.158^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.dyna-ns.net`
NS	`ns2.dyna-ns.net`
		A	2400:cb00:2049:1::a29f:1805^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	2400:cb00:2049:1::a29f:1905^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.24.5^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
		A	162.159.25.5^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.dyna-ns.net`
SOA	`ns1.dyna-ns.net`hostmaster@microsofttoken.com 2026-04-03 #1

`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=1777016431

⚠️ On DNS blocklist: tif

Subdomains

www.microsofttoken.com

Same first word

microsofttoken.com

DNS History

6 records (3 active, 3 former)

●NSns1.dyna-ns.net2026-04-11 → 2026-04-24 · 3 obs

○ 2017-12-04 11:04:50
● 2026-04-11 23:58:16
● 2026-04-24 07:51:46

●NSns2.dyna-ns.net2026-04-11 → 2026-04-24 · 3 obs

○ 2017-12-04 11:04:50
● 2026-04-11 23:58:16
● 2026-04-24 07:51:46

○NSns25.domaincontrol.com2017-12-04 → 2017-12-04 · 3 obs

● 2017-12-04 11:04:50
○ 2026-04-11 23:58:16
○ 2026-04-24 07:51:46

○NSns26.domaincontrol.com2017-12-04 → 2017-12-04 · 3 obs

● 2017-12-04 11:04:50
○ 2026-04-11 23:58:16
○ 2026-04-24 07:51:46

●A185.53.179.1282026-04-11 → 2026-04-24 · 3 obs

○ 2017-12-04 11:04:50
● 2026-04-11 23:58:16
● 2026-04-24 07:51:46

○A50.63.202.622017-12-04 → 2017-12-04 · 3 obs

● 2017-12-04 11:04:50
○ 2026-04-11 23:58:16
○ 2026-04-24 07:51:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
microsofttoken.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.25.5

NS records: ns2.dyna-ns.net, ns1.dyna-ns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for microsofttoken.com (unsigned zone)

⏱️ Timing

Total: 234ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`185.53.179.128`
NS	2	`ns2.dyna-ns.net, ns1.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.microsofttoke`

Analysis

Hierarchy

microsofttoken.com is the parent of www.microsofttoken.com.

IP Addresses

microsofttoken.com points to IP number 185.53.179.128.

For instance, other host names llantasventa.com, zeventy.com, fiberopticcabling.net, movewithmaureen.com and domains.1usd1.com share IP numbers with microsofttoken.com.

Name Servers

microsofttoken.com is delegated to two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.

microsofttoken.com uses the same name server setup as other domains such as iu.team, your.st, personal-city.com, 8vogue.com and yous.com.

Host names with four IPs:

ns1.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1a5c, 2400:cb00:2049:1::a29f:1b9e, 162.159.26.92 and 162.159.27.158

ns2.dyna-ns.net points to: 2400:cb00:2049:1::a29f:1805, 2400:cb00:2049:1::a29f:1905, 162.159.24.5 and 162.159.25.5

microsofttoken.com - robtex.com