`bonding-hearts.com`

DNSSEC	⚠️ Not signed
A	192.0.78.186^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.211^{🇺🇸 Automattic192.0.78.0/24 Route Object}
NS	`ns1.wordpress.com` ⭐
		A	2a04:fa87:ffff::c6b5:7409^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns1.wordpress.com`
		A	198.181.116.9^{🇺🇸 Automattic198.181.116.0/24 Route Object}
			PTR	`ns1.wordpress.com`
NS	`ns2.wordpress.com`
		A	2a04:fa87:ffff::c6b5:7509^{🇮🇪 Automattic2a04:fa87:ffff::/48}
			PTR	`ns2.wordpress.com`
		A	198.181.117.9^{🇺🇸 Automattic198.181.117.0/24 Route Object}
			PTR	`ns2.wordpress.com`
NS	`ns3.wordpress.com`
		A	2620:115:c00f::c000:4a09^{🇺🇸 Automattic2620:115:c00f::/48 Route6 Object}
			PTR	`ns3.wordpress.com`
		A	192.0.74.9^{🇺🇸 Automattic192.0.74.0/24 Route Object}
			PTR	`ns3.wordpress.com`
MX	`mx1.titan.email` ⭐
		A	3.213.54.98^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-213-54-98.compute-1.amazonaws.com`
		A	32.195.144.151
			PTR	`ec2-32-195-144-151.compute-1.amazonaws.com`
		A	34.205.167.2^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-205-167-2.compute-1.amazonaws.com`
MX	`mx2.titan.email`⁽²⁰⁾
		A	3.213.54.98^{🇺🇸 Amazon3.208.0.0/12 EC2 IAD prefix}
			PTR	`ec2-3-213-54-98.compute-1.amazonaws.com`
		A	32.195.144.151
			PTR	`ec2-32-195-144-151.compute-1.amazonaws.com`
		A	34.205.167.2^{🇺🇸 Amazon34.192.0.0/12 EC2 IAD prefix}
			PTR	`ec2-34-205-167-2.compute-1.amazonaws.com`
TXT	`v=spf1 include:spf.titan.email include:_spf.wpcloud.com ~all`
SOA	`ns1.wordpress.com`hostmaster@wordpress.com 2005-07-18 #58

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

Same first word

bonding-hearts.com

DNS History

16 records (7 active, 9 former)

○NSns-cloud-e1.googledomains.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

○NSns-cloud-e2.googledomains.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

○NSns-cloud-e3.googledomains.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

○NSns-cloud-e4.googledomains.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

●NSns1.wordpress.com2026-02-24 → 2026-04-25 · 3 obs

○ 2018-06-14 15:06:42
● 2026-02-24 08:12:00
● 2026-04-25 01:08:52

●NSns2.wordpress.com2026-02-24 → 2026-04-25 · 3 obs

○ 2018-06-14 15:06:42
● 2026-02-24 08:12:00
● 2026-04-25 01:08:52

●NSns3.wordpress.com2026-02-24 → 2026-04-25 · 3 obs

○ 2018-06-14 15:06:42
● 2026-02-24 08:12:00
● 2026-04-25 01:08:52

○MXalt1.aspmx.l.google.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

○MXalt2.aspmx.l.google.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

○MXalt3.aspmx.l.google.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

○MXalt4.aspmx.l.google.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

○MXaspmx.l.google.com2018-06-14 → 2018-06-14 · 3 obs

● 2018-06-14 15:06:42
○ 2026-02-24 08:12:00
○ 2026-04-25 01:08:52

●MXmx1.titan.email2026-02-24 → 2026-04-25 · 3 obs

○ 2018-06-14 15:06:42
● 2026-02-24 08:12:00
● 2026-04-25 01:08:52

●MXmx2.titan.email2026-02-24 → 2026-04-25 · 3 obs

○ 2018-06-14 15:06:42
● 2026-02-24 08:12:00
● 2026-04-25 01:08:52

●A192.0.78.1862026-02-24 → 2026-04-25 · 2 obs

● 2026-02-24 08:12:00
● 2026-04-25 01:08:52

●A192.0.78.2112026-02-24 → 2026-04-25 · 2 obs

● 2026-02-24 08:12:00
● 2026-04-25 01:08:52

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, f.gtld-servers.net, k.gtld-servers.net, c.gtld-servers.net...	-
bonding-hearts.com	ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com	6 records

✅ Authoritative Response

Server:198.181.117.9

NS records: ns1.wordpress.com, ns2.wordpress.com, ns3.wordpress.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for bonding-hearts.com (unsigned zone)

⏱️ Timing

Total: 389ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.186, 192.0.78.211`
NS	3	`ns2.wordpress.com, ns1.wordpress.com...`
MX	2	`mx1.titan.email (pri: 10), mx2.titan.email (pri: 20)`
TXT	1	`v=spf1 include:spf.titan.email include:_`
SOA	1	`ns1.wordpress.com hostmaster.wordpress.c`

📌 Glue Records Collected

Total: 6

Out-of-bailiwick: 6 (ns1.wordpress.com, ns1.wordpress.com, ns2.wordpress.com...)

Analysis

IP Addresses

bonding-hearts.com points to two IP numbers: 192.0.78.186 and 192.0.78.211.

Other host names such as getreadygo.com, blogemlak.com, schneider-modehaus.de, corporate.mystays.com and totalms.com share IPs with bonding-hearts.com.

Name Servers

bonding-hearts.com is delegated to three name servers: ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.

bonding-hearts.com at least partially shares name servers with other domains, for example taugrim.com, amyfairclothdesigns.com, azthet.com, altheasadventures.com and hockeyprospecting.com.

Host names with two IP numbers:

ns1.wordpress.com points to 2a04:fa87:ffff::c6b5:7409 and 198.181.116.9

ns2.wordpress.com points to 2a04:fa87:ffff::c6b5:7509 and 198.181.117.9

ns3.wordpress.com points to 2620:115:c00f::c000:4a09 and 192.0.74.9

Mail Servers

Two mail servers handle bonding-hearts.com: mx1.titan.email and mx2.titan.email.

bonding-hearts.com shares the same mail server setup as other domains, including vocalremover.org, porosdemokrasi.com, examsaway.com, theboxflow.com and bastianstolk.com.

bonding-hearts.com shares some mail servers with other domains, at least partially, for instance edstickets.cl, myanmarpolestar.com, nationalprinting.net and dovelandschool.com.