`google-reputation.com`

DNSSEC	⚠️ Not signed
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`
MX	`mx2.mymailsystem.com` ⭐
		A	51.38.30.81^{🇫🇷 OVH51.38.0.0/16}
			PTR	`send4.mymailsystem.com`
MX	`mx.mymailsystem.com`⁽²⁰⁾
		A	91.134.37.172^{🇫🇷 OVH91.134.0.0/16}
			PTR	`send2.mymailsystem.com`
TXT	`v=spf1 a mx include:spf.mymailsystem.com -all`
SOA	`ns1.dyna-ns.net`hostmaster@google-reputation.com 2026-03-19 #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=1774372982

Same first word

google-reputation.com

DNS History

4 records (4 active, 0 former)

●NSns1.dyna-ns.net2026-02-20 → 2026-03-24 · 2 obs

● 2026-02-20 12:12:10
● 2026-03-24 17:40:00

●NSns2.dyna-ns.net2026-02-20 → 2026-03-24 · 2 obs

● 2026-02-20 12:12:10
● 2026-03-24 17:40:00

●MXmx.mymailsystem.com2026-02-20 → 2026-03-24 · 2 obs

● 2026-02-20 12:12:10
● 2026-03-24 17:40:00

●MXmx2.mymailsystem.com2026-02-20 → 2026-03-24 · 2 obs

● 2026-02-20 12:12:10
● 2026-03-24 17:40:00

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, j.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net...	-
google-reputation.com	ns2.dyna-ns.net, ns1.dyna-ns.net	-

✅ Authoritative Response

Server:162.159.27.158

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for google-reputation.com (unsigned zone)

⏱️ Timing

Total: 583ms | Queries: -

📄 Records

Type	Count	Sample Data
NS	2	`ns1.dyna-ns.net, ns2.dyna-ns.net`
MX	2	`mx.mymailsystem.com (pri: 10), mx2.mymailsystem.com (pri: 20)`
TXT	1	`v=spf1 a mx include:spf.mymailsystem.com`
SOA	1	`ns1.dyna-ns.net hostmaster.google-reputa`

Analysis

Name Servers

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

google-reputation.com uses the same name server setup as other domains such as xn--qprr84e.com, mxwhhrtn.com, 569vips.com, ekka.in and uo(0x6a697a7a).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

Mail Servers

Two mail servers mx2.mymailsystem.com and mx.mymailsystem.com handle google-reputation.com.

google-reputation.com shares the same mail server setup as other domains, for instance galdi-us.com, wirestride.com, growwithheir.com, omnistreammatrix.com and upgrade-surveysparrow.com.

google-reputation.com shares some mail servers with other domains to some extent, for instance mymailsystem.com and eclipsenova.com.

Host names with one IP number:

mx2.mymailsystem.com points to: 51.38.30.81.

mx.mymailsystem.com points to: 91.134.37.172.

google-reputation.com - robtex.com