synorg.com - dns.ninja

`synorg.com`

DNSSEC	⚠️ Not signed
A	66.45.246.141^{🇺🇸 NJIIX-166.45.224.0/19 NJIIX.net 110B Meadowlands Pkwy Secaucus, NJ 07094}
NS	`ns1.domainrecover.com` ⭐ ⚠️ Not in parent delegation
		A	149.248.38.58^{🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix}
			PTR	`149.248.38.58.vultrusercontent.com`
NS	`ns1.serverhome.com` ⚠️ Not in zone NS records
		A	149.248.38.58^{🇺🇸 AS-VULTR149.248.32.0/20 Vultr Assigned Prefix}
			PTR	`149.248.38.58.vultrusercontent.com`
NS	`ns2.domainrecover.com` ⚠️ Not in parent delegation
		A	199.247.16.62^{🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix}
			PTR	`199.247.16.62.vultrusercontent.com`
NS	`ns2.serverhome.com` ⚠️ Not in zone NS records
		A	199.247.16.62^{🇩🇪 AS-VULTR199.247.16.0/21 Vultr Assigned Prefix}
			PTR	`199.247.16.62.vultrusercontent.com`
TXT	`yGjyZf7SHD`
SOA	`ns1.domainrecover.com`hostmaster@domainreover.com serial=1623031840

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

Same first word

synorg.com

Similar names

gryson.net

songry.com

ongrys.pl

gnyrso.org

syngro.net

songry.blogspot.com.es

gryson.be

syngro.co

orgsyn.org

gryson.cn

rongys.com

grynos.net

gryson.com

syngro.com

orgsyn.de

nysorg.com

grosny.com

gryson.org

snorgy.com

ryongs.com

syngro.org

gornys.com

DNS History

19 records (5 active, 14 former)

○NSdns1.name-services.com2007-11-11 → 2007-11-11 · 3 obs

● 2007-11-11 22:33:26
○ 2015-06-28 16:43:40
○ 2026-07-01 16:15:06

○NSdns2.name-services.com2007-11-11 → 2007-11-11 · 3 obs

● 2007-11-11 22:33:26
○ 2015-06-28 16:43:40
○ 2026-07-01 16:15:06

○NSdns3.name-services.com2007-11-11 → 2007-11-11 · 3 obs

● 2007-11-11 22:33:26
○ 2015-06-28 16:43:40
○ 2026-07-01 16:15:06

○NSdns4.name-services.com2007-11-11 → 2007-11-11 · 3 obs

● 2007-11-11 22:33:26
○ 2015-06-28 16:43:40
○ 2026-07-01 16:15:06

○NSdns5.name-services.com2007-11-11 → 2007-11-11 · 3 obs

● 2007-11-11 22:33:26
○ 2015-06-28 16:43:40
○ 2026-07-01 16:15:06

●NSns1.domainrecover.com2026-04-06 → 2026-07-01 · 3 obs

○ 2017-01-11 21:58:40
● 2026-04-06 23:43:08
● 2026-07-01 16:15:06

○NSns1.dsredirection.com2015-11-12 → 2016-05-03 · 5 obs

○ 2015-06-28 16:43:40
● 2015-11-12 03:42:10
● 2016-05-03 00:09:04
○ 2017-01-11 21:58:40
○ 2026-07-01 16:15:06

●NSns1.serverhome.com2026-04-06 → 2026-07-01 · 3 obs

○ 2017-01-11 21:58:40
● 2026-04-06 23:43:08
● 2026-07-01 16:15:06

●NSns2.domainrecover.com2026-04-06 → 2026-07-01 · 3 obs

○ 2017-01-11 21:58:40
● 2026-04-06 23:43:08
● 2026-07-01 16:15:06

○NSns2.dsredirection.com2015-11-12 → 2016-05-03 · 5 obs

○ 2015-06-28 16:43:40
● 2015-11-12 03:42:10
● 2016-05-03 00:09:04
○ 2017-01-11 21:58:40
○ 2026-07-01 16:15:06

●NSns2.serverhome.com2026-04-06 → 2026-07-01 · 3 obs

○ 2017-01-11 21:58:40
● 2026-04-06 23:43:08
● 2026-07-01 16:15:06

○MXmxs1.serverhome.com2015-06-28 → 2020-01-15 · 8 obs

○ 2007-11-11 22:33:26
● 2015-06-28 16:43:40
● 2016-01-28 23:44:40
○ 2016-05-03 00:09:04
● 2017-01-11 21:58:40
● 2020-01-15 23:51:30
○ 2026-04-06 23:43:08
○ 2026-07-01 16:15:06

○MXmxs2.serverhome.com2015-06-28 → 2020-01-15 · 8 obs

○ 2007-11-11 22:33:26
● 2015-06-28 16:43:40
● 2016-01-28 23:44:40
○ 2016-05-03 00:09:04
● 2017-01-11 21:58:40
● 2020-01-15 23:51:30
○ 2026-04-06 23:43:08
○ 2026-07-01 16:15:06

○A141.8.230.202015-06-28 → 2016-05-03 · 5 obs

○ 2007-11-11 22:33:26
● 2015-06-28 16:43:40
● 2016-05-03 00:09:04
○ 2017-01-11 21:58:40
○ 2026-07-01 16:15:06

●A66.45.246.1412017-01-11 → 2026-07-01 · 5 obs

○ 2016-05-03 00:09:04
● 2017-01-11 21:58:40
○ 2020-01-15 23:51:30
● 2026-04-06 23:43:08
● 2026-07-01 16:15:06

○A8.15.231.1152007-11-11 → 2007-11-11 · 3 obs

● 2007-11-11 22:33:26
○ 2015-06-28 16:43:40
○ 2026-07-01 16:15:06

○CNAMEnews.serverhome.com2015-06-28 → 2016-05-03 · 5 obs

○ 2007-11-11 22:33:26
● 2015-06-28 16:43:40
● 2016-05-03 00:09:04
○ 2017-01-11 21:58:40
○ 2026-07-01 16:15:06

○CNAMEsnews.serverhome.com2017-01-11 → 2020-01-15 · 5 obs

○ 2016-05-03 00:09:04
● 2017-01-11 21:58:40
● 2020-01-15 23:51:30
○ 2026-04-06 23:43:08
○ 2026-07-01 16:15:06

○CNAMEthie5ku9.dsgeneration.com2015-11-12 → 2016-05-03 · 5 obs

○ 2015-06-28 16:43:40
● 2015-11-12 03:42:10
● 2016-05-03 00:09:04
○ 2017-01-11 21:58:40
○ 2026-07-01 16:15:06

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
synorg.com	ns1.serverhome.com, ns2.serverhome.com	2 records

✅ Authoritative Response

Server:149.248.38.58

NS records: ns1.serverhome.com, ns2.serverhome.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for synorg.com (unsigned zone)

⏱️ Timing

Total: 385ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`66.45.246.141`
NS	2	`NS2.DOMAINRECOVER.com, NS1.DOMAINRECOVER.com`
TXT	1	`yGjyZf7SHD`
SOA	1	`ns1.domainrecover.com hostmaster.domainr`

📌 Glue Records Collected

Total: 2

Out-of-bailiwick: 2 (ns1.serverhome.com, ns2.serverhome.com)

Analysis

IP Addresses

synorg.com resolves to just one IP address, 66.45.246.141.

Two other host names, along with covas.com, invalsi.com and chezpascal.com, also share IP numbers with synorg.com.

Name Servers

The NS records for synorg.com point to four name servers: ns1.domainrecover.com, ns2.domainrecover.com, ns1.serverhome.com and ns2.serverhome.com.

At least some of synorg.com's name servers are shared with other domains, for example spbauto.com, in-law.com, sadogorod.com and two more.

These name servers tend to be deployed in combination with the name servers ns2.servering.com and ns.servering.com.

ns1.domainrecover.com, ns2.domainrecover.com, ns1.serverhome.com and ns2.serverhome.com each point to exactly one IP address. ns1.domainrecover.com directs to 149.248.38.58, ns2.domainrecover.com directs to 199.247.16.62, ns1.serverhome.com directs to 149.248.38.58 and ns2.serverhome.com directs to 199.247.16.62. Two pairs share an IP: ns1.domainrecover.com and ns1.serverhome.com share 149.248.38.58, and ns2.domainrecover.com and ns2.serverhome.com share 199.247.16.62.

Host names pointing to 149.248.38.58 IP addresses: ns1.domainrecover.com and ns1.serverhome.com.

Host names pointing to 199.247.16.62 IP addresses: ns2.domainrecover.com and ns2.serverhome.com.