`date4meet.com`

DNSSEC	⚠️ Not signed
A	107.173.89.214^{🇺🇸 Colocrossing-AS107.173.88.0/22}
		PTR	`107-173-89-214-host.colocrossing.com`
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@date4meet.com 2026-04-14 #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=1778319996

Same first word

date4meet.com

DNS History

5 records (3 active, 2 former)

○NSali.ns.cloudflare.com2017-12-19 → 2017-12-19 · 3 obs

● 2017-12-19 09:06:42
○ 2026-02-17 09:45:04
○ 2026-05-09 10:05:34

○NSchuck.ns.cloudflare.com2017-12-19 → 2017-12-19 · 3 obs

● 2017-12-19 09:06:42
○ 2026-02-17 09:45:04
○ 2026-05-09 10:05:34

●NSns1.dyna-ns.net2026-02-17 → 2026-05-09 · 3 obs

○ 2017-12-19 09:06:42
● 2026-02-17 09:45:04
● 2026-05-09 10:05:34

●NSns2.dyna-ns.net2026-02-17 → 2026-05-09 · 3 obs

○ 2017-12-19 09:06:42
● 2026-02-17 09:45:04
● 2026-05-09 10:05:34

●A107.173.89.2142026-02-17 → 2026-05-09 · 2 obs

● 2026-02-17 09:45:04
● 2026-05-09 10:05:34

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:162.159.26.92

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for date4meet.com (unsigned zone)

⏱️ Timing

Total: 572ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`107.173.89.214`
NS	2	`ns2.dyna-ns.net, ns1.dyna-ns.net`
SOA	1	`ns1.dyna-ns.net hostmaster.date4meet.com`

Analysis

IP Addresses

date4meet.com resolves to one IP number: 107.173.89.214.

Name Servers

date4meet.com's delegation uses two name servers: ns1.dyna-ns.net and ns2.dyna-ns.net.

date4meet.com uses the same name server setup as other domains, such as kientruc24h.com, mipresento.com, advantagefcu-verify.sbs, venunair.com and passgates.com.

date4meet.com at least partially shares name servers with other domains, for example igjit.com.

Host names with four IP numbers:

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

date4meet.com - robtex.com

date4meet.com

com