`diglore.com`

DNSSEC	⚠️ Not signed
A	3.215.53.39^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
		PTR	`ec2-3-215-53-39.compute-1.amazonaws.com`
NS	`kim.ns.cloudflare.com` ⭐
		A	2606:4700:50::adf5:3a7e^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c07e^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`kim.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:207e^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`kim.ns.cloudflare.com`
		A	108.162.192.126^{🇺🇸 Cloudflare108.162.192.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	172.64.32.126^{🇺🇸 Cloudflare172.64.32.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
		A	173.245.58.126^{🇺🇸 Cloudflare173.245.58.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`kim.ns.cloudflare.com`
NS	`mcgrory.ns.cloudflare.com`
		A	2606:4700:58::a29f:2caa^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`mcgrory.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c3aa^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`mcgrory.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:23aa^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`mcgrory.ns.cloudflare.com`
		A	108.162.195.170^{🇺🇸 Cloudflare108.162.195.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`mcgrory.ns.cloudflare.com`
		A	162.159.44.170^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`mcgrory.ns.cloudflare.com`
		A	172.64.35.170^{🇺🇸 Cloudflare172.64.35.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`mcgrory.ns.cloudflare.com`
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`
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	`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`
TXT	`v=spf1 include:_spf.mx.cloudflare.net ~all`
SOA	`kim.ns.cloudflare.com`dns@cloudflare.com serial=2409695874

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

Same first word

diglore.com

Similar names

ergolid.com

olgierd.pl

direlog.com

lidergo.com

idleorg.org

rogedil.com

roegild.dk

olridge.com

rogledi.com

goldire.com

logride.com

golderi.ru

leogrid.app

rigoled.com

geroldi.com

digerol.com

ergolid.com.pl

riegold.de

leogrid.com

erigold.com

goldrei.com

gordeli.com

gloried.com

ergolid.pl

golider.com

ledgrio.com

lodrige.com

olgierd.eu

deligro.com

godlier.de

gelidor.ru

goldier.com

giroled.es

geroldi.it

gloried.shop

ergolid.eu

idleorg.com

olgierd.com

delrigo.com

olgierd.org

dreilog.at

gidroel.ru

godlier.com

igrodel.ru

doegirl.com

elgrido.com

roegild.nu

ldoerig.ch

igolder.com

DNS History

24 records (6 active, 18 former)

○NSdns1.registrar-servers.com2026-02-27 → 2026-05-27 · 5 obs

○ 2018-07-01 14:50:54
● 2026-02-27 20:00:18
● 2026-05-27 02:12:08
○ 2026-06-03 03:07:04
○ 2026-07-21 06:27:14

○NSdns2.registrar-servers.com2026-02-27 → 2026-05-27 · 5 obs

○ 2018-07-01 14:50:54
● 2026-02-27 20:00:18
● 2026-05-27 02:12:08
○ 2026-06-03 03:07:04
○ 2026-07-21 06:27:14

●NSkim.ns.cloudflare.com2026-06-03 → 2026-07-21 · 3 obs

○ 2026-05-27 02:12:08
● 2026-06-03 03:07:04
● 2026-07-21 06:27:14

●NSmcgrory.ns.cloudflare.com2026-06-03 → 2026-07-21 · 3 obs

○ 2026-05-27 02:12:08
● 2026-06-03 03:07:04
● 2026-07-21 06:27:14

○NSns21.domaincontrol.com2018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○NSns22.domaincontrol.com2018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○MXeforward1.registrar-servers.com2026-02-27 → 2026-02-27 · 3 obs

● 2026-02-27 20:00:18
○ 2026-07-21 06:27:10
○ 2026-07-21 06:27:14

○MXeforward2.registrar-servers.com2026-02-27 → 2026-02-27 · 3 obs

● 2026-02-27 20:00:18
○ 2026-07-21 06:27:10
○ 2026-07-21 06:27:14

○MXeforward3.registrar-servers.com2026-02-27 → 2026-02-27 · 3 obs

● 2026-02-27 20:00:18
○ 2026-07-21 06:27:10
○ 2026-07-21 06:27:14

○MXeforward4.registrar-servers.com2026-02-27 → 2026-02-27 · 3 obs

● 2026-02-27 20:00:18
○ 2026-07-21 06:27:10
○ 2026-07-21 06:27:14

○MXeforward5.registrar-servers.com2026-02-27 → 2026-02-27 · 3 obs

● 2026-02-27 20:00:18
○ 2026-07-21 06:27:10
○ 2026-07-21 06:27:14

●MXroute1.mx.cloudflare.net2026-07-21 → 2026-07-21 · 3 obs

○ 2026-02-27 20:00:18
● 2026-07-21 06:27:10
● 2026-07-21 06:27:14

●MXroute2.mx.cloudflare.net2026-07-21 → 2026-07-21 · 3 obs

○ 2026-02-27 20:00:18
● 2026-07-21 06:27:10
● 2026-07-21 06:27:14

●MXroute3.mx.cloudflare.net2026-07-21 → 2026-07-21 · 3 obs

○ 2026-02-27 20:00:18
● 2026-07-21 06:27:10
● 2026-07-21 06:27:14

○A184.168.221.332018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○A184.168.221.402018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○A184.168.221.492018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○A184.168.221.502018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○A184.168.221.572018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○A192.64.119.772026-02-27 → 2026-05-27 · 5 obs

○ 2018-07-01 14:50:54
● 2026-02-27 20:00:18
● 2026-05-27 02:12:08
○ 2026-06-03 03:07:04
○ 2026-07-21 06:27:14

●A3.215.53.392026-06-03 → 2026-07-21 · 3 obs

○ 2026-05-27 02:12:08
● 2026-06-03 03:07:04
● 2026-07-21 06:27:14

○A50.63.202.522018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○A50.63.202.552018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

○A50.63.202.622018-07-01 → 2018-07-01 · 3 obs

● 2018-07-01 14:50:54
○ 2026-02-27 20:00:18
○ 2026-07-21 06:27:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	k.gtld-servers.net, i.gtld-servers.net, l.gtld-servers.net, e.gtld-servers.net...	-
diglore.com	kim.ns.cloudflare.com, mcgrory.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.195.170

NS records: kim.ns.cloudflare.com, mcgrory.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for diglore.com (unsigned zone)

⏱️ Timing

Total: 199ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`3.215.53.39`
NS	2	`kim.ns.cloudflare.com, mcgrory.ns.cloudflare.com`
MX	3	`route1.mx.cloudflare.net (pri: 10), route2.mx.cloudflare.net (pri: 20)...`
TXT	1	`v=spf1 include:_spf.mx.cloudflare.net ~a`
SOA	1	`kim.ns.cloudflare.com dns.cloudflare.com`

📌 Glue Records Collected

Total: 12

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

Analysis

IP Addresses

diglore.com resolves to one IP address: 3.215.53.39.

Host names like ec2-3-215-53-39.compute-1.amazonaws.com are further examples that share IP numbers with diglore.com.

Name Servers

Two name servers handle the delegation for diglore.com: kim.ns.cloudflare.com and mcgrory.ns.cloudflare.com.

diglore.com uses the same name servers as several other domains — among them 7mcn.center, alo789.contact, gmnc.me and two more.

The name servers of diglore.com overlap at least partially with those of other domains — among them jingjiyi.com, xinyongke.com, googlepay-test.pages.dev and two more.

These name servers commonly appear alongside the name servers casey.ns.cloudflare.com and todd.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

kim.ns.cloudflare.com resolves to 108.162.192.126, 172.64.32.126 and 173.245.58.126 among others, with 3 other IP addresses in total.

mcgrory.ns.cloudflare.com resolves to 108.162.195.170, 162.159.44.170 and 172.64.35.170 among others, with 3 other IP addresses in total.

Mail Servers

Mail for diglore.com is routed through three mail servers — route1.mx.cloudflare.net, route2.mx.cloudflare.net and route3.mx.cloudflare.net.

diglore.com has at least partial mail server overlap with other domains such as foreign-office.com, blograg.com, lad-global.com and two more.

Hostnames that resolve to 6 IP addresses:

route1.mx.cloudflare.net resolves to 162.159.205.11, 162.159.205.12 and 162.159.205.13 among others, with 3 other IP addresses in total.

route2.mx.cloudflare.net resolves to 162.159.205.17, 162.159.205.18 and 162.159.205.19 among others, with 3 other IP addresses in total.

route3.mx.cloudflare.net resolves to 162.159.205.23, 162.159.205.24 and 162.159.205.25 among others, with 3 other IP addresses in total.

diglore.com - robtex.com

diglore.com

com

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

IP Addresses

Name Servers

Mail Servers

`diglore.com`

`com`