ensogram.com - dns.ninja

`ensogram.com`

DNSSEC	⚠️ Not signed
A	173.254.104.26^{🇺🇸 EIGI173.254.0.0/17 Unified Layer}
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
TXT	`v=spf1 include:eu-sender.zohobooks.com`
SOA	`ns1.bluehost.com`root@box2251.bluehost.com 2023-06-26 #0

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

Same first word

ensogram.com

Similar names

DNS History

19 records (8 active, 11 former)

○NSdns1.name-services.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

○NSdns2.name-services.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

○NSdns3.name-services.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

○NSdns4.name-services.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

○NSdns5.name-services.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

●NSns1.bluehost.com2026-03-28 → 2026-07-22 · 3 obs

○ 2017-08-18 16:46:12
● 2026-03-28 08:33:02
● 2026-07-22 15:47:20

●NSns2.bluehost.com2026-03-28 → 2026-07-22 · 3 obs

○ 2017-08-18 16:46:12
● 2026-03-28 08:33:02
● 2026-07-22 15:47:20

●MXalt1.aspmx.l.google.com2015-06-25 → 2026-07-22 · 2 obs

● 2015-06-25 01:08:54
● 2026-07-22 15:47:20

●MXalt2.aspmx.l.google.com2015-06-25 → 2026-07-22 · 2 obs

● 2015-06-25 01:08:54
● 2026-07-22 15:47:20

●MXalt3.aspmx.l.google.com2026-03-28 → 2026-07-22 · 3 obs

○ 2017-08-18 16:46:12
● 2026-03-28 08:33:02
● 2026-07-22 15:47:20

●MXalt4.aspmx.l.google.com2026-03-28 → 2026-07-22 · 3 obs

○ 2017-08-18 16:46:12
● 2026-03-28 08:33:02
● 2026-07-22 15:47:20

●MXaspmx.l.google.com2015-06-25 → 2026-07-22 · 2 obs

● 2015-06-25 01:08:54
● 2026-07-22 15:47:20

○MXaspmx2.googlemail.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

○MXaspmx3.googlemail.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

○MXaspmx4.googlemail.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

○MXaspmx5.googlemail.com2015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

●A173.254.104.262026-03-28 → 2026-07-22 · 3 obs

○ 2017-08-18 16:46:12
● 2026-03-28 08:33:02
● 2026-07-22 15:47:20

○A69.89.31.1042015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

○A74.220.195.312015-06-25 → 2017-08-18 · 4 obs

● 2015-06-25 01:08:54
● 2017-08-18 16:46:12
○ 2026-03-28 08:33:02
○ 2026-07-22 15:47:20

🔍 DNS Trace

📋 Delegation Chain

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

✅ Authoritative Response

Server:162.159.25.175

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ensogram.com (unsigned zone)

⏱️ Timing

Total: 612ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`173.254.104.26`
NS	2	`ns2.bluehost.com, ns1.bluehost.com`
MX	5	`alt4.aspmx.l.google.com (pri: 10), alt2.aspmx.l.google.com (pri: 5)...`
TXT	1	`v=spf1 include:eu-sender.zohobooks.com`
SOA	1	`ns1.bluehost.com root.box2251.bluehost.c`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

ensogram.com has exactly one IP address — 173.254.104.26.

decosters.com, mail.ron-gordon.com, www.shinerightnow.com plus two other host names have IP numbers in common with ensogram.com.

Name Servers

ensogram.com uses two name servers for its delegation: ns1.bluehost.com and ns2.bluehost.com.

The name server configuration of ensogram.com is shared with other domains, for instance derwyn.com, terepair.com, tekcaliper.com and two others.

ensogram.com has a partial name server overlap with other domains — among them unhitec.com and bellarosa.ec.

ns1.bluehost.com directs to 162.159.24.80 and ns2.bluehost.com directs to 162.159.25.175; each host name points to exactly one IP number.

Mail Servers

Mail for ensogram.com is handled by five mail servers, namely aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

At least some of the mail servers used by ensogram.com are shared with other domains: ns500693.ns500693.ns500693.ns500734.ns500699.ns500693.ns500699.ns500699.ns500588.ns500693.ns500693.ns500699.ns500602.dtrkdll.com, brianhales.com, ns500698.ns500698.ns500698.ns500758.ns500758.ns500735.ns500736.ns500708.ns500708.ns500698.ns500698.ns500576.ns500619.ns500652.ns500576.trackreceptor.com and two others among them.

These mail servers often appear in conjunction with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names pointing to two IP addresses:

aspmx.l.google.com directs traffic to 142.251.163.27 and 2607:f8b0:4004:c1b::1a.

alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.