`push-forward.blog`

DNSSEC	⚠️ Not signed
A	192.0.78.24^{🇺🇸 Automattic192.0.78.0/24 Route Object}
A	192.0.78.25^{🇺🇸 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`
SOA	`ns1.wordpress.com`hostmaster@wordpress.com 2026-08-09 #3

`blog`

	DNSSEC	🔒 Signed (DS record present)
	NS	`prd-fzp-07.corp.cira.ca` ⭐
	NS	`a.ns.nic.blog`
	NS	`b.ns.nic.blog`
	NS	`c.ns.nic.blog`
	NS	`d.ns.nic.blog`
	SOA	`prd-fzp-07.corp.cira.ca`admin-dns@cira.ca serial=2608131200

Same first word

push-forward.blog

DNS History

5 records (5 active, 0 former)

●NSns1.wordpress.com2026-08-13 → 2026-08-13 · 2 obs

● 2026-08-13 00:12:52
● 2026-08-13 12:22:08

●NSns2.wordpress.com2026-08-13 → 2026-08-13 · 2 obs

● 2026-08-13 00:12:52
● 2026-08-13 12:22:08

●NSns3.wordpress.com2026-08-13 → 2026-08-13 · 2 obs

● 2026-08-13 00:12:52
● 2026-08-13 12:22:08

●A192.0.78.242026-08-13 → 2026-08-13 · 2 obs

● 2026-08-13 00:12:52
● 2026-08-13 12:22:08

●A192.0.78.252026-08-13 → 2026-08-13 · 2 obs

● 2026-08-13 00:12:52
● 2026-08-13 12:22:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
blog	a.ns.nic.blog, b.ns.nic.blog, c.ns.nic.blog, d.ns.nic.blog	8 records
push-forward.blog	ns3.wordpress.com, ns2.wordpress.com, ns1.wordpress.com	-

✅ Authoritative Response

Server:198.181.116.9

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

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for push-forward.blog (unsigned zone)

⏱️ Timing

Total: 584ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`192.0.78.25, 192.0.78.24`
NS	3	`ns2.wordpress.com, ns3.wordpress.com...`
SOA	1	`ns1.wordpress.com hostmaster.wordpress.c`

📌 Glue Records Collected

Total: 8

In-bailiwick: 8 (a.ns.nic.blog, a.ns.nic.blog, b.ns.nic.blog...)

Analysis

IP Addresses

push-forward.blog points to the IP addresses 192.0.78.24 and 192.0.78.25

Additional host names — gforge.com, adamturk.com, bjmail.org and two others — share IP numbers with push-forward.blog.

Name Servers

DNS for push-forward.blog is handled by three authoritative name servers: ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com.

At least some of push-forward.blog's name servers are shared with other domains, for example bangcollections.com, housefly.us, thomaspurcaro.com and two more.

Three hostnames — ns1.wordpress.com, ns2.wordpress.com and ns3.wordpress.com — each have two IP addresses: ns1.wordpress.com has 198.181.116.9 and 2a04:fa87:ffff::c6b5:7409, ns2.wordpress.com has 198.181.117.9 and 2a04:fa87:ffff::c6b5:7509, and ns3.wordpress.com has 192.0.74.9 and 2620:115:c00f::c000:4a09.

push-forward.blog - robtex.com