phillycodeworks.com - dns.ninja

`phillycodeworks.com`

DNSSEC	⚠️ Not signed
A	104.255.172.234^{🇺🇸 APTUM104.255.172.0/24 Peer1 Route Object}
		PTR	`romeo.iwebfusion.net`
NS	`r1.core-dns.net` ⭐ ⚠️ Not in parent delegation
		A	64.34.217.23^{🇺🇸 APTUM64.34.216.0/22 Peer1 Route Object}
			PTR	`romeo.core-dns.net`
NS	`p1.core-dns.net` ⚠️ Not in zone NS records
		A	104.255.172.234^{🇺🇸 APTUM104.255.172.0/24 Peer1 Route Object}
			PTR	`romeo.iwebfusion.net`
NS	`p2.core-dns.net` ⚠️ Not in zone NS records
		A	104.255.172.235^{🇺🇸 APTUM104.255.172.0/24 Peer1 Route Object}
			PTR	`cxv7az2qsi4c.team.homefibresystems.com`
NS	`r2.core-dns.net` ⚠️ Not in parent delegation
		A	64.34.217.26^{🇺🇸 APTUM64.34.216.0/22 Peer1 Route Object}
			PTR	`romeo.iwebfusion.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c07::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bc-in-f27.1e100.net`
		A	173.194.45.27^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1b^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-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::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`v=spf1 ip4:64.34.217.23 include:relay.mailchannels.net +a +mx +ip4:104.255.17...`
TXT	`google-site-verification=pRlRP_nxoCPKjH-Tz8p5nP6RWGoeMUr3psEI54v0L6s`
SOA	`r1.core-dns.net`root@romeo.core-dns.net 2026-05-26 #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=1781886985

Same first word

phillycodeworks.com

DNS History

14 records (10 active, 4 former)

○NSns1.digitalocean.com2015-05-26 → 2016-07-12 · 4 obs

● 2015-05-26 00:26:02
● 2016-07-12 23:57:04
○ 2017-04-04 16:46:14
○ 2026-06-19 16:58:24

○NSns2.digitalocean.com2015-05-26 → 2016-07-12 · 4 obs

● 2015-05-26 00:26:02
● 2016-07-12 23:57:04
○ 2017-04-04 16:46:14
○ 2026-06-19 16:58:24

○NSns3.digitalocean.com2015-05-26 → 2016-07-12 · 4 obs

● 2015-05-26 00:26:02
● 2016-07-12 23:57:04
○ 2017-04-04 16:46:14
○ 2026-06-19 16:58:24

●NSp1.core-dns.net2017-04-04 → 2026-06-19 · 3 obs

○ 2016-07-12 23:57:04
● 2017-04-04 16:46:14
● 2026-06-19 16:58:24

●NSp2.core-dns.net2017-04-04 → 2026-06-19 · 3 obs

○ 2016-07-12 23:57:04
● 2017-04-04 16:46:14
● 2026-06-19 16:58:24

●NSr1.core-dns.net2026-04-01 → 2026-06-19 · 3 obs

○ 2017-04-04 16:46:14
● 2026-04-01 02:24:26
● 2026-06-19 16:58:24

●NSr2.core-dns.net2026-04-01 → 2026-06-19 · 3 obs

○ 2017-04-04 16:46:14
● 2026-04-01 02:24:26
● 2026-06-19 16:58:24

●MXalt1.aspmx.l.google.com2015-05-26 → 2026-06-19 · 2 obs

● 2015-05-26 00:26:02
● 2026-06-19 16:58:24

●MXalt2.aspmx.l.google.com2015-05-26 → 2026-06-19 · 2 obs

● 2015-05-26 00:26:02
● 2026-06-19 16:58:24

●MXalt3.aspmx.l.google.com2015-05-26 → 2026-06-19 · 2 obs

● 2015-05-26 00:26:02
● 2026-06-19 16:58:24

●MXalt4.aspmx.l.google.com2015-05-26 → 2026-06-19 · 2 obs

● 2015-05-26 00:26:02
● 2026-06-19 16:58:24

●MXaspmx.l.google.com2015-05-26 → 2026-06-19 · 2 obs

● 2015-05-26 00:26:02
● 2026-06-19 16:58:24

●A104.255.172.2342017-04-04 → 2026-06-19 · 3 obs

○ 2016-07-12 23:57:04
● 2017-04-04 16:46:14
● 2026-06-19 16:58:24

○A107.170.145.1412015-05-26 → 2016-07-12 · 4 obs

● 2015-05-26 00:26:02
● 2016-07-12 23:57:04
○ 2017-04-04 16:46:14
○ 2026-06-19 16:58:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	m.gtld-servers.net, f.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net...	-
phillycodeworks.com	p1.core-dns.net, p2.core-dns.net	-

✅ Authoritative Response

Server:104.255.172.234

NS records: p1.core-dns.net, p2.core-dns.net

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for phillycodeworks.com (unsigned zone)

⏱️ Timing

Total: 3434ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`104.255.172.234`
NS	2	`r1.core-dns.net, r2.core-dns.net`
MX	5	`alt2.aspmx.l.google.com (pri: 5), alt3.aspmx.l.google.com (pri: 10)...`
TXT	2	`v=spf1 ip4:64.34.217.23 include:relay.ma, google-site-verification=pRlRP_nxoCPKjH-`
SOA	1	`r1.core-dns.net root.romeo.core-dns.net`

Analysis

IP Addresses

phillycodeworks.com resolves to one IP address: 104.255.172.234.

bwave.com, sharptownfiredept.com, cybra.net and two other host names share IP numbers with phillycodeworks.com.

Name Servers

The authoritative name servers for phillycodeworks.com are p1.core-dns.net, p2.core-dns.net, r1.core-dns.net and r2.core-dns.net.

At least some of phillycodeworks.com's name servers are shared with other domains, for example nwwildflowers.com, 215.41.181.in-addr.arpa, aforier.com and two more.

These name servers tend to co-occur with h1.core-dns.net, ns1.iwebfusion.net, ns2.iwebfusion.net and 5 other name servers in the same DNS delegations.

Each of the four hosts p1.core-dns.net, p2.core-dns.net, r1.core-dns.net and r2.core-dns.net points to a single IP address — p1.core-dns.net points to 104.255.172.234, p2.core-dns.net points to 104.255.172.235, r1.core-dns.net points to 64.34.217.23 and r2.core-dns.net points to 64.34.217.26.

Mail Servers

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

phillycodeworks.com has at least partial mail server overlap with other domains such as tungli.net, menziesautomotivegroup.com, acenteredself.net and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com maps to two IP addresses — 173.194.45.27 and 2607:f8b0:4004:c07::1b.

alt1.aspmx.l.google.com maps to two IP addresses — 108.177.123.27 and 2800:3f0:4003:c0f::1b.

alt2.aspmx.l.google.com maps to two IP addresses — 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com maps to two IP addresses — 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com maps to two IP addresses — 172.253.157.27 and 2a00:1450:400c:c23::1a.