writeforacause.com - dns.ninja

`writeforacause.com`

DNSSEC	⚠️ Not signed
A	162.241.253.186^{🇺🇸 ORACLE-OCI-31898162.241.252.0/22 Google}
		PTR	`box5812.bluehost.com`
NS	`ns1.bluehost.com` ⭐
		A	162.159.24.80^{Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns1.bluehost.com`
NS	`ns2.bluehost.com`
		A	162.159.25.175^{Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`ns2.bluehost.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c27::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadsk-in-f27.1e100.net`
		A	173.194.45.26^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
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.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 +ip4:162.241.253.186 +include:spf.protection.outlook.com -all`
SOA	`ns1.bluehost.com`root@box5812.bluehost.com 2026-08-03 #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=1786496419

Same first word

writeforacause.com

DNS History

13 records (8 active, 5 former)

●NSns1.bluehost.com2026-03-14 → 2026-08-12 · 3 obs

○ 2020-01-13 04:49:54
● 2026-03-14 22:36:30
● 2026-08-12 01:26:48

●NSns2.bluehost.com2026-03-14 → 2026-08-12 · 3 obs

○ 2020-01-13 04:49:54
● 2026-03-14 22:36:30
● 2026-08-12 01:26:48

○NSns71.domaincontrol.com2016-06-20 → 2017-02-13 · 4 obs

● 2016-06-20 07:44:48
● 2017-02-13 03:39:00
○ 2020-01-13 04:49:54
○ 2026-08-12 01:26:48

○NSns72.domaincontrol.com2016-06-20 → 2017-02-13 · 4 obs

● 2016-06-20 07:44:48
● 2017-02-13 03:39:00
○ 2020-01-13 04:49:54
○ 2026-08-12 01:26:48

●MXalt1.aspmx.l.google.com2026-03-14 → 2026-08-12 · 3 obs

○ 2020-01-13 04:49:54
● 2026-03-14 22:36:30
● 2026-08-12 01:26:48

●MXalt2.aspmx.l.google.com2026-03-14 → 2026-08-12 · 3 obs

○ 2020-01-13 04:49:54
● 2026-03-14 22:36:30
● 2026-08-12 01:26:48

●MXalt3.aspmx.l.google.com2026-03-14 → 2026-08-12 · 3 obs

○ 2020-01-13 04:49:54
● 2026-03-14 22:36:30
● 2026-08-12 01:26:48

●MXalt4.aspmx.l.google.com2026-03-14 → 2026-08-12 · 3 obs

○ 2020-01-13 04:49:54
● 2026-03-14 22:36:30
● 2026-08-12 01:26:48

●MXaspmx.l.google.com2026-03-14 → 2026-08-12 · 3 obs

○ 2020-01-13 04:49:54
● 2026-03-14 22:36:30
● 2026-08-12 01:26:48

○MXmailstore1.secureserver.net2016-06-20 → 2017-02-13 · 4 obs

● 2016-06-20 07:44:48
● 2017-02-13 03:39:00
○ 2020-01-13 04:49:54
○ 2026-08-12 01:26:48

○MXsmtp.secureserver.net2016-06-20 → 2017-02-13 · 4 obs

● 2016-06-20 07:44:48
● 2017-02-13 03:39:00
○ 2020-01-13 04:49:54
○ 2026-08-12 01:26:48

●A162.241.253.1862026-03-14 → 2026-08-12 · 3 obs

○ 2020-01-13 04:49:54
● 2026-03-14 22:36:30
● 2026-08-12 01:26:48

○A50.63.202.372016-06-20 → 2017-02-13 · 4 obs

● 2016-06-20 07:44:48
● 2017-02-13 03:39:00
○ 2020-01-13 04:49:54
○ 2026-08-12 01:26:48

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	l.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...	-
writeforacause.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 writeforacause.com (unsigned zone)

⏱️ Timing

Total: 351ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`162.241.253.186`
NS	2	`ns1.bluehost.com, ns2.bluehost.com`
MX	5	`alt2.aspmx.l.google.com (pri: 5), alt4.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 +ip4:162.241.253.186 +include:spf`
SOA	1	`ns1.bluehost.com root.box5812.bluehost.c`

📌 Glue Records Collected

Total: 2

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

Analysis

IP Addresses

writeforacause.com points to a single IP number: 162.241.253.186.

Additional host names — avalon-logistics.com, rentparisapartment.com, jpascholarships.com and two others — share IP numbers with writeforacause.com.

Name Servers

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

writeforacause.com shares its name server setup with other domains, including asocmedia.com, searlesgiftlist.com, lfcspecialties.com and two others.

Each of ns1.bluehost.com and ns2.bluehost.com has one IP address: ns1.bluehost.com uses 162.159.24.80 and ns2.bluehost.com uses 162.159.25.175.

Mail Servers

Five mail servers handle writeforacause.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

writeforacause.com shares mail servers — at least in part — with other domains, including metacoleman.com, liaqsa.com, californiapercussion.com and two others.

These mail servers are frequently paired with the mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com.

Host names with two IP numbers:

aspmx.l.google.com directs traffic to 173.194.45.26 and 2607:f8b0:4004:c27::1b.

alt1.aspmx.l.google.com directs traffic to 192.178.234.27 and 2800:3f0:4003:c14::1a.

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

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

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