yfgr.com - dns.ninja

`yfgr.com`

DNSSEC	⚠️ Not signed
A	64.190.63.222^{🇩🇪 SEDO64.190.62.0/23 -NET2-PI}
NS	`ns1.sedoparking.com` ⭐
		A	3.130.216.63^{🇺🇸 Amazon3.130.0.0/16 EC2 CMH prefix}
			PTR	`ec2-3-130-216-63.us-east-2.compute.amazonaws.com`
		A	91.195.241.8^{🇩🇪 SEDO91.195.240.0/23 -NET-PI}
NS	`ns2.sedoparking.com`
		A	34.211.188.210^{🇺🇸 Amazon34.208.0.0/12 EC2 PDX prefix}
			PTR	`ec2-34-211-188-210.us-west-2.compute.amazonaws.com`
		A	91.195.240.8^{🇩🇪 SEDO91.195.240.0/23 -NET-PI}
MX	`localhost` ⭐
TXT	`v=spf1 -all`
SOA	`ns1.sedoparking.com`hostmaster@sedo.de 2018-05-16 #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=1785965889

Same first word

yfgr.cn

yfgr.com

Similar names

gryf.pl

gryf.trafficmanager.net

gryf.sk

gyrf.net

yrfg.cn

frgy.cn

fgry.com

fryg.net

rgfy.com

gryf.net

ygfr.com.cn

gryf.mielno.pl

gryf.tv

gyrf.io

gryf.org

fgry.df.gov.br

gryf.pomorze.pl

fgyr.cn

fyrg.cn

fygr.io

ygrf.com

gfyr.com

rygf.com

gryf.wroclaw.pl

gryf.dk

gryf.de

ryfg.cn

gryf.com

gyrf.com

ygfr.com

rfyg.com

gyfr.cn

gryf.info

grfy.com

yrgf.cn

ygfr.net

gyfr.xyz

fygr.cn

yrfg.com

fryg.cn

ygrf.com.cn

rygf.net

yrgf.com

grfy.net

fgry.cn

gryf.czest.pl

DNS History

21 records (4 active, 17 former)

○NSdns1.iidns.com2016-03-21 → 2017-03-27 · 4 obs

● 2016-03-21 16:01:44
● 2017-03-27 23:54:56
○ 2026-02-25 11:01:22
○ 2026-08-05 21:41:26

○NSdns2.iidns.com2016-03-21 → 2016-03-22 · 4 obs

● 2016-03-21 16:01:44
● 2016-03-22 18:57:06
○ 2017-03-27 23:54:56
○ 2026-08-05 21:41:26

○NSdns3.iidns.com2016-03-21 → 2016-03-22 · 4 obs

● 2016-03-21 16:01:44
● 2016-03-22 18:57:06
○ 2017-03-27 23:54:56
○ 2026-08-05 21:41:26

○NSdns4.iidns.com2016-03-21 → 2016-03-22 · 4 obs

● 2016-03-21 16:01:44
● 2016-03-22 18:57:06
○ 2017-03-27 23:54:56
○ 2026-08-05 21:41:26

○NSdns5.iidns.com2016-03-21 → 2016-03-22 · 4 obs

● 2016-03-21 16:01:44
● 2016-03-22 18:57:06
○ 2017-03-27 23:54:56
○ 2026-08-05 21:41:26

○NSdns6.iidns.com2016-03-21 → 2016-03-22 · 4 obs

● 2016-03-21 16:01:44
● 2016-03-22 18:57:06
○ 2017-03-27 23:54:56
○ 2026-08-05 21:41:26

○NSns1.ename.net2026-02-25 → 2026-06-07 · 4 obs

○ 2017-03-27 23:54:56
● 2026-02-25 11:01:22
● 2026-06-07 14:32:42
○ 2026-08-05 21:41:26

●NSns1.sedoparking.com2026-08-05 → 2026-08-05 · 2 obs

○ 2026-06-07 14:32:42
● 2026-08-05 21:41:26

○NSns2.ename.net2026-02-25 → 2026-06-07 · 4 obs

○ 2017-03-27 23:54:56
● 2026-02-25 11:01:22
● 2026-06-07 14:32:42
○ 2026-08-05 21:41:26

●NSns2.sedoparking.com2026-08-05 → 2026-08-05 · 2 obs

○ 2026-06-07 14:32:42
● 2026-08-05 21:41:26

●MXlocalhost2026-08-05 → 2026-08-05 · 1 obs

● 2026-08-05 21:41:26

○A103.241.230.1352017-03-27 → 2017-03-27 · 4 obs

○ 2016-03-22 18:57:06
● 2017-03-27 23:54:56
○ 2026-02-25 11:01:22
○ 2026-08-05 21:41:26

○A103.241.230.1372017-03-27 → 2017-03-27 · 4 obs

○ 2016-03-22 18:57:06
● 2017-03-27 23:54:56
○ 2026-02-25 11:01:22
○ 2026-08-05 21:41:26

○A103.241.230.1382017-03-27 → 2017-03-27 · 4 obs

○ 2016-03-22 18:57:06
● 2017-03-27 23:54:56
○ 2026-02-25 11:01:22
○ 2026-08-05 21:41:26

○A103.241.230.1402017-03-27 → 2017-03-27 · 4 obs

○ 2016-03-22 18:57:06
● 2017-03-27 23:54:56
○ 2026-02-25 11:01:22
○ 2026-08-05 21:41:26

○A107.167.19.722016-03-22 → 2016-03-22 · 4 obs

○ 2016-01-26 19:38:48
● 2016-03-22 18:57:06
○ 2017-03-27 23:54:56
○ 2026-08-05 21:41:26

○A107.167.19.732016-03-22 → 2016-03-22 · 4 obs

○ 2016-01-26 19:38:48
● 2016-03-22 18:57:06
○ 2017-03-27 23:54:56
○ 2026-08-05 21:41:26

●A64.190.63.2222026-08-05 → 2026-08-05 · 2 obs

○ 2026-02-25 11:01:22
● 2026-08-05 21:41:26

○A64.62.224.2532015-06-09 → 2016-01-26 · 4 obs

● 2015-06-09 08:46:52
● 2016-01-26 19:38:48
○ 2016-03-22 18:57:06
○ 2026-08-05 21:41:26

○CNAMEcs.ename.net2016-03-22 → 2017-03-27 · 5 obs

● 2016-03-22 18:57:06
○ 2016-07-27 14:15:32
● 2017-03-27 23:54:56
○ 2026-02-25 11:01:22
○ 2026-08-05 21:41:26

○CNAMEcs1.ename.net2026-02-25 → 2026-03-31 · 5 obs

○ 2017-03-27 23:54:56
● 2026-02-25 11:01:22
● 2026-03-31 03:58:22
○ 2026-06-07 14:32:42
○ 2026-08-05 21:41:26

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	g.gtld-servers.net, e.gtld-servers.net, b.gtld-servers.net, a.gtld-servers.net...	-
yfgr.com	ns1.sedoparking.com, ns2.sedoparking.com	2 records

✅ Authoritative Response

Server:91.195.241.8

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for yfgr.com (unsigned zone)

⏱️ Timing

Total: 331ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`64.190.63.222`
NS	2	`ns2.sedoparking.com, ns1.sedoparking.com`
MX	1	`localhost (pri: 0)`
TXT	1	`v=spf1 -all`
SOA	1	`ns1.sedoparking.com hostmaster.sedo.de`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

yfgr.com resolves to one IP address: 64.190.63.222.

placemploi.fr, mail.fets-office.de, stables.pl and two other host names share IP numbers with yfgr.com.

Name Servers

yfgr.com is served by two delegated name servers, ns1.sedoparking.com and ns2.sedoparking.com.

yfgr.com uses the same name servers as several other domains — among them ns2.leopardstownracing.com, bhnd.de, mail.luxurypark.com and two more.

The name servers for yfgr.com overlap at least in part with those of other domains, including webvisitenkarten.net and assesscapability.com.

Each of the two host names carries two IP addresses: ns1.sedoparking.com points to 3.130.216.63 and 91.195.241.8, and ns2.sedoparking.com points to 34.211.188.210 and 91.195.240.8.

Mail Servers

Mail for yfgr.com is handled by a single mail server, localhost.

yfgr.com uses an identical mail server configuration to several other domains — among them regueira.eu, mail.healthyyou.net, dia.se and two more.