`tech-m-s.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3033::6815:4b41^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3033::ac43:d7b8^{🇺🇸 Cloudflare2606:4700:3033::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.75.65^{Cloudflare104.21.64.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.215.184^{🇺🇸 Cloudflare172.67.208.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`kiki.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3ab4^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kiki.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c0b4^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kiki.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:20b4^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kiki.ns.cloudflare.com`
		A	108.162.192.180^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kiki.ns.cloudflare.com`
		A	172.64.32.180^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kiki.ns.cloudflare.com`
		A	173.245.58.180^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kiki.ns.cloudflare.com`
NS	`kip.ns.cloudflare.com`
		A	2606:4700:58::adf5:3b80^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kip.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c180^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kip.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2180^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kip.ns.cloudflare.com`
		A	108.162.193.128^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kip.ns.cloudflare.com`
		A	172.64.33.128^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kip.ns.cloudflare.com`
		A	173.245.59.128^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kip.ns.cloudflare.com`
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`
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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.75.65, 172.67.215.184
		IPv6 hints	2606:4700:3033::6815:4b41, 2606:4700:3033::ac43:d7b8
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=254, name=cloudflare-ech.com
SOA	`kiki.ns.cloudflare.com`dns@cloudflare.com serial=2403586435

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

Same first word

tech-m-s.com

DNS History

17 records (9 active, 8 former)

●NSkiki.ns.cloudflare.com2026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

●NSkip.ns.cloudflare.com2026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

○NSns41.domaincontrol.com2017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 13:24:20
○ 2026-04-16 06:16:02
○ 2026-05-11 10:19:14

○NSns42.domaincontrol.com2017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 13:24:20
○ 2026-04-16 06:16:02
○ 2026-05-11 10:19:14

○MXalt1.aspmx.l.google.com2017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 13:24:20
○ 2026-04-16 06:16:02
○ 2026-05-11 10:19:14

○MXalt2.aspmx.l.google.com2017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 13:24:20
○ 2026-04-16 06:16:02
○ 2026-05-11 10:19:14

○MXaspmx.l.google.com2017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 13:24:20
○ 2026-04-16 06:16:02
○ 2026-05-11 10:19:14

○MXaspmx2.googlemail.com2017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 13:24:20
○ 2026-04-16 06:16:02
○ 2026-05-11 10:19:14

○MXaspmx3.googlemail.com2017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 13:24:20
○ 2026-04-16 06:16:02
○ 2026-05-11 10:19:14

●MXroute1.mx.cloudflare.net2026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

●MXroute2.mx.cloudflare.net2026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

●MXroute3.mx.cloudflare.net2026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

●A104.21.75.652026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

●A172.67.215.1842026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

○A184.168.221.472017-08-13 → 2017-08-13 · 3 obs

● 2017-08-13 13:24:20
○ 2026-04-16 06:16:02
○ 2026-05-11 10:19:14

●A2606:4700:3033::6815:4b412026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

●A2606:4700:3033::ac43:d7b82026-04-16 → 2026-05-11 · 3 obs

○ 2017-08-13 13:24:20
● 2026-04-16 06:16:02
● 2026-05-11 10:19:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, c.gtld-servers.net, k.gtld-servers.net, b.gtld-servers.net...	-
tech-m-s.com	kip.ns.cloudflare.com, kiki.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.193.128

NS records: kip.ns.cloudflare.com, kiki.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for tech-m-s.com (unsigned zone)

⏱️ Timing

Total: 246ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.215.184, 104.21.75.65`
AAAA	2	`2606:4700:3033::ac43:d7b8, 2606:4700:3033::6815:4b41`
NS	2	`kiki.ns.cloudflare.com, kip.ns.cloudflare.com`
MX	3	`route3.mx.cloudflare.net (pri: 19), route2.mx.cloudflare.net (pri: 22)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`kiki.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

tech-m-s.com maps to four IP numbers: 2606:4700:3033::6815:4b41, 2606:4700:3033::ac43:d7b8, 104.21.75.65 and 172.67.215.184.

Other host names, for instance oleksandriya-libr.rv.ua, www.ncellrecharge.com, vivape.co, giantnews.org and haojunpin.com share IP numbers with tech-m-s.com.

Name Servers

Two name servers kiki.ns.cloudflare.com and kip.ns.cloudflare.com handle delegation for tech-m-s.com.

tech-m-s.com uses the same name server setup as other domains, for example routerp.com, signal.md, nuwaves.org, jimjfstraw.com and aspirerankings.com.

tech-m-s.com partially shares name servers with other domains; examples include 0.a.7.c.f.2.0.6.2.ip6.arpa, docu.sk, isthegovernmentopen.com, treating-bipolar-disorder.com and lafron.com.

these name servers are commonly used with the name servers walt.ns.cloudflare.com.

Host names with six IP numbers: kiki.ns.cloudflare.com points to: 2606:4700:50::adf5:3ab4, 2803:f800:50::6ca2:c0b4, 2a06:98c1:50::ac40:20b4, 108.162.192.180, 172.64.32.180 and 173.245.58.180; kip.ns.cloudflare.com points to: 2606:4700:58::adf5:3b80, 2803:f800:50::6ca2:c180, 2a06:98c1:50::ac40:2180, 108.162.193.128, 172.64.33.128 and 173.245.59.128.

Mail Servers

tech-m-s.com is handled by three mail servers: route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

tech-m-s.com shares some mail servers with other domains, at least partially, such as ews.ir, kensicosoapbar.com, fede.co.za, robsheppard.com and x16.in.

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.

tech-m-s.com - robtex.com

tech-m-s.com

com

Same first word

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`tech-m-s.com`

`com`