databloom.com - dns.ninja

`databloom.com`

DNSSEC	⚠️ Not signed
A	15.223.11.93^{🇨🇦 Amazon15.222.0.0/15 EC2 YUL prefix}
		PTR	`ec2-15-223-11-93.ca-central-1.compute.amazonaws.com`
NS	`ns01.databloom.com` ⭐
NS	`dns1.databloom.com` ⚠️ Not in zone NS records
		A	174.143.157.66^{🇺🇸 RACKSPACE-DFW174.143.0.0/16 Rackspace Managed Hosting, 9725 Datapoint DR, Suite 100, San Antonio, TX 78229}
			PTR	`174-143-157-66.static.cloud-ips.com`
NS	`dns2.databloom.com` ⚠️ Not in zone NS records
NS	`ns.databloom.com`
		A	174.143.157.66^{🇺🇸 RACKSPACE-DFW174.143.0.0/16 Rackspace Managed Hosting, 9725 Datapoint DR, Suite 100, San Antonio, TX 78229}
			PTR	`174-143-157-66.static.cloud-ips.com`
NS	`ns1.databloom.com` ⚠️ Not in zone NS records
		A	174.143.157.66^{🇺🇸 RACKSPACE-DFW174.143.0.0/16 Rackspace Managed Hosting, 9725 Datapoint DR, Suite 100, San Antonio, TX 78229}
			PTR	`174-143-157-66.static.cloud-ips.com`
NS	`ns2.databloom.com`
		A	174.143.157.66^{🇺🇸 RACKSPACE-DFW174.143.0.0/16 Rackspace Managed Hosting, 9725 Datapoint DR, Suite 100, San Antonio, TX 78229}
			PTR	`174-143-157-66.static.cloud-ips.com`
NS	`ns3.databloom.com` ⚠️ Not in zone NS records
		A	174.143.157.66^{🇺🇸 RACKSPACE-DFW174.143.0.0/16 Rackspace Managed Hosting, 9725 Datapoint DR, Suite 100, San Antonio, TX 78229}
			PTR	`174-143-157-66.static.cloud-ips.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c23::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadrs-in-f26.1e100.net`
		A	64.233.180.26^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f26.1e100.net`
			PTR	`pe-in-f26.1e100.net`
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}
			PTR	`lcscld-in-f26.1e100.net`
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.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`aspmx2.googlemail.com`⁽³⁰⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.26^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f26.1e100.net`
MX	`aspmx3.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400b:c01::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`di-in-f27.1e100.net`
		A	74.125.193.26^{🇺🇸 Google74.125.193.0/24}
			PTR	`di-in-f26.1e100.net`
			PTR	`ig-in-f26.1e100.net`
MX	`aspmx4.googlemail.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}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`aspmx5.googlemail.com`⁽³⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
TXT	`google-site-verification=PBOWiLM4sTGNhKprCO02-dlio8sWRgNnofN5nuDVoho`
SOA	`ns.databloom.com`root@databloom.com 2026-05-25 #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=1785451807

Subdomains

ns3.databloom.com

dns1.databloom.com

ns.databloom.com

ns2.databloom.com

ns1.databloom.com

Same first word

databloom.co.uk

databloom.net

databloom.shop

databloom.com

databloom.one

Similar names

bloomdata.com

DNS History

20 records (15 active, 5 former)

●NSdns1.databloom.com2009-01-18 → 2026-07-30 · 5 obs

● 2009-01-18 20:01:40
○ 2015-06-24 08:49:48
○ 2018-01-22 09:53:26
● 2026-02-22 06:05:58
● 2026-07-30 23:16:40

●NSdns2.databloom.com2009-01-18 → 2026-07-30 · 5 obs

● 2009-01-18 20:01:40
○ 2015-06-24 08:49:48
○ 2018-01-22 09:53:26
● 2026-02-22 06:05:58
● 2026-07-30 23:16:40

○NSmule.databloom.com2009-01-18 → 2009-01-18 · 3 obs

● 2009-01-18 20:01:40
○ 2015-06-24 08:49:48
○ 2026-07-30 23:16:40

●NSns.databloom.com2009-01-18 → 2026-07-30 · 2 obs

● 2009-01-18 20:01:40
● 2026-07-30 23:16:40

●NSns01.databloom.com2026-02-22 → 2026-07-30 · 3 obs

○ 2018-01-22 09:53:26
● 2026-02-22 06:05:58
● 2026-07-30 23:16:40

●NSns1.databloom.com2009-01-18 → 2026-07-30 · 2 obs

● 2009-01-18 20:01:40
● 2026-07-30 23:16:40

●NSns2.databloom.com2009-01-18 → 2026-07-30 · 5 obs

● 2009-01-18 20:01:40
○ 2015-06-24 08:49:48
○ 2018-01-22 09:53:26
● 2026-02-22 06:05:58
● 2026-07-30 23:16:40

●NSns3.databloom.com2009-01-18 → 2026-07-30 · 2 obs

● 2009-01-18 20:01:40
● 2026-07-30 23:16:40

●MXalt1.aspmx.l.google.com2015-06-24 → 2026-07-30 · 3 obs

○ 2009-01-18 20:01:40
● 2015-06-24 08:49:48
● 2026-07-30 23:16:40

●MXalt2.aspmx.l.google.com2015-06-24 → 2026-07-30 · 3 obs

○ 2009-01-18 20:01:40
● 2015-06-24 08:49:48
● 2026-07-30 23:16:40

●MXaspmx.l.google.com2015-06-24 → 2026-07-30 · 3 obs

○ 2009-01-18 20:01:40
● 2015-06-24 08:49:48
● 2026-07-30 23:16:40

●MXaspmx2.googlemail.com2015-06-24 → 2026-07-30 · 3 obs

○ 2009-01-18 20:01:40
● 2015-06-24 08:49:48
● 2026-07-30 23:16:40

●MXaspmx3.googlemail.com2015-06-24 → 2026-07-30 · 3 obs

○ 2009-01-18 20:01:40
● 2015-06-24 08:49:48
● 2026-07-30 23:16:40

●MXaspmx4.googlemail.com2015-06-24 → 2026-07-30 · 3 obs

○ 2009-01-18 20:01:40
● 2015-06-24 08:49:48
● 2026-07-30 23:16:40

●MXaspmx5.googlemail.com2015-06-24 → 2026-07-30 · 3 obs

○ 2009-01-18 20:01:40
● 2015-06-24 08:49:48
● 2026-07-30 23:16:40

○MXbridge.databloom.com2009-01-18 → 2009-01-18 · 3 obs

● 2009-01-18 20:01:40
○ 2015-06-24 08:49:48
○ 2026-07-30 23:16:40

●A15.223.11.932026-02-22 → 2026-07-30 · 3 obs

○ 2018-01-22 09:53:26
● 2026-02-22 06:05:58
● 2026-07-30 23:16:40

○A162.209.3.1362015-06-24 → 2015-11-06 · 5 obs

○ 2009-01-18 20:01:40
● 2015-06-24 08:49:48
● 2015-11-06 07:17:44
○ 2016-02-10 20:43:44
○ 2026-07-30 23:16:40

○A174.143.157.662016-02-10 → 2018-01-22 · 5 obs

○ 2015-11-06 07:17:44
● 2016-02-10 20:43:44
● 2018-01-22 09:53:26
○ 2026-02-22 06:05:58
○ 2026-07-30 23:16:40

○A204.138.56.822009-01-18 → 2009-01-18 · 3 obs

● 2009-01-18 20:01:40
○ 2015-06-24 08:49:48
○ 2026-07-30 23:16:40

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
databloom.com	ns.databloom.com, ns2.databloom.com, ns3.databloom.com, dns1.databloom.com...	7 records

✅ Authoritative Response

Server:174.143.157.66

NS records: ns.databloom.com, ns2.databloom.com, ns3.databloom.com, dns1.databloom.com, dns2.databloom.com, ns1.databloom.com, ns01.databloom.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for databloom.com (unsigned zone)

⏱️ Timing

Total: 227ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`15.223.11.93`
NS	3	`ns1.databloom.com, ns3.databloom.com...`
MX	7	`ASPMX3.GOOGLEMAIL.com (pri: 30), ASPMX4.GOOGLEMAIL.com (pri: 30)...`
TXT	2	`google-site-verification=PBOWiLM4sTGNhKp, v=spf1 include:_spf.google.com ~all`
SOA	1	`ns.databloom.com root.databloom.com`

📌 Glue Records Collected

Total: 7

In-bailiwick: 7 (ns.databloom.com, ns2.databloom.com, ns3.databloom.com...)

Analysis

Hierarchy

ns3.databloom.com, dns1.databloom.com, ns.databloom.com, ns2.databloom.com and ns1.databloom.com are all subdomains of databloom.com.

IP Addresses

databloom.com resolves to just one IP address, 15.223.11.93.

ec2-15-223-11-93.ca-central-1.compute.amazonaws.com, for instance, is one of the other host names sharing IP numbers with databloom.com.

Name Servers

databloom.com delegates authority to 7 name servers: dns1.databloom.com, dns2.databloom.com, ns01.databloom.com plus 4 other.

The name servers of databloom.com overlap at least partially with those of other domains — among them dinoble.com, maxwattofficial.com, torontocorsets.com and two more.

Host names that point to one IP address:

dns1.databloom.com has the IP address 174.143.157.66.

ns1.databloom.com has the IP address 174.143.157.66.

ns2.databloom.com has the IP address 174.143.157.66.

ns3.databloom.com has the IP address 174.143.157.66.

ns.databloom.com has the IP address 174.143.157.66.

These host names point to 174.143.157.66: dns1.databloom.com, ns1.databloom.com, ns2.databloom.com and two others.

Mail Servers

databloom.com has 7 mail servers — aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx4.googlemail.com plus 4 other.

There is at least a partial MX overlap between databloom.com and other domains, including ns500731.ns500671.ns500731.ns500742.ns500742.ns500705.ns500705.ns500688.ns500705.ns500705.ns500291.ns500649.ns500291.ns500291.ns500131.lustychickser.com, ns500599.ns500724.ns500737.ns500724.ns500599.ns500599.ns500737.ns500599.ns500724.ns500583.ns500599.www.yummyflingsfinder.com, szkolapaderewski.krakow.pl and two others.

These mail servers tend to appear in combination with mail servers aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and 3 others.

Host names that have two IP addresses:

aspmx2.googlemail.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1b.

aspmx3.googlemail.com directs traffic to 74.125.193.26 and 2a00:1450:400b:c01::1b.

aspmx4.googlemail.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

aspmx5.googlemail.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.

aspmx.l.google.com directs traffic to 64.233.180.26 and 2607:f8b0:4004:c23::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.26 and 2a00:1450:400b:c02::1b.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 2800:3f0:4003:c0f::1b IP addresses each.

Both aspmx2.googlemail.com and alt1.aspmx.l.google.com resolve to 108.177.123.26 IP addresses each.