berkeley.systems - dns.ninja

`berkeley.systems`

DNSSEC	⚠️ Not signed
A	54.161.150.96^{🇺🇸 Amazon54.160.0.0/14 EC2 IAD prefix}
		PTR	`ec2-54-161-150-96.compute-1.amazonaws.com`
NS	`ns77.domaincontrol.com` ⭐
		A	2603:5:21c4::31^{🇺🇸 GODADDY-DNS2603:5:21c0::/44}
			PTR	`ns77.domaincontrol.com`
		A	97.74.108.49^{🇺🇸 GODADDY-DNS97.74.108.0/23}
			PTR	`ns77.domaincontrol.com`
NS	`ns78.domaincontrol.com`
		A	2603:5:22c4::31^{🇺🇸 GODADDY-DNS2603:5:22c0::/44}
			PTR	`ns78.domaincontrol.com`
		A	173.201.76.49^{🇺🇸 GODADDY-DNS173.201.76.0/23}
			PTR	`ns78.domaincontrol.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c19::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bk-in-f27.1e100.net`
		A	172.253.62.27^{🇺🇸 Google172.253.62.0/24}
			PTR	`bc-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	`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: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`
TXT	`google-site-verification=h1ifQv3AYhu_6-S_pTUb9jaRP5MFvCanssny4FrKWaQ`
TXT	`v=spf1 ip4: 123.123.123.123 include:_spf.google.com ~all`
SOA	`ns77.domaincontrol.com`dns@jomax.net 2021-05-12 #0

`systems`

	DNSSEC	🔒 Signed (DS record present)
	NS	`v0n0.nic.systems` ⭐
	NS	`v0n1.nic.systems`
	NS	`v0n2.nic.systems`
	NS	`v0n3.nic.systems`
	NS	`v2n0.nic.systems`
	NS	`v2n1.nic.systems`
	SOA	`v0n0.nic.systems`hostmaster@donuts.email serial=1784170661

Same first word

Similar names

eberkley.com

leekerby.com

leybeker.com

rebelkey.com

DNS History

10 records (8 active, 2 former)

●NSns77.domaincontrol.com2015-06-20 → 2026-07-16 · 2 obs

● 2015-06-20 07:30:00
● 2026-07-16 03:15:46

●NSns78.domaincontrol.com2015-06-20 → 2026-07-16 · 2 obs

● 2015-06-20 07:30:00
● 2026-07-16 03:15:46

●MXalt1.aspmx.l.google.com2015-06-20 → 2026-07-16 · 2 obs

● 2015-06-20 07:30:00
● 2026-07-16 03:15:46

●MXalt2.aspmx.l.google.com2015-06-20 → 2026-07-16 · 2 obs

● 2015-06-20 07:30:00
● 2026-07-16 03:15:46

●MXaspmx.l.google.com2015-06-20 → 2026-07-16 · 2 obs

● 2015-06-20 07:30:00
● 2026-07-16 03:15:46

●MXaspmx2.googlemail.com2015-06-20 → 2026-07-16 · 2 obs

● 2015-06-20 07:30:00
● 2026-07-16 03:15:46

●MXaspmx3.googlemail.com2015-06-20 → 2026-07-16 · 2 obs

● 2015-06-20 07:30:00
● 2026-07-16 03:15:46

○A50.63.202.602015-06-20 → 2016-02-24 · 4 obs

● 2015-06-20 07:30:00
● 2016-02-24 20:37:58
○ 2016-03-12 20:37:14
○ 2026-07-16 03:15:46

●A54.161.150.962026-03-29 → 2026-07-16 · 3 obs

○ 2016-12-02 22:47:16
● 2026-03-29 08:54:54
● 2026-07-16 03:15:46

○A54.167.172.1562016-03-12 → 2016-12-02 · 5 obs

○ 2016-02-24 20:37:58
● 2016-03-12 20:37:14
● 2016-12-02 22:47:16
○ 2026-03-29 08:54:54
○ 2026-07-16 03:15:46

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
systems	v0n0.nic.systems, v0n2.nic.systems, v2n0.nic.systems, v0n1.nic.systems...	12 records
berkeley.systems	ns77.domaincontrol.com, ns78.domaincontrol.com	-

✅ Authoritative Response

Server:173.201.76.49

NS records: ns77.domaincontrol.com, ns78.domaincontrol.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for berkeley.systems (unsigned zone)

⏱️ Timing

Total: 401ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`54.161.150.96`
NS	2	`ns77.domaincontrol.com, ns78.domaincontrol.com`
MX	5	`alt1.aspmx.l.google.com (pri: 20), alt2.aspmx.l.google.com (pri: 20)...`
TXT	2	`google-site-verification=h1ifQv3AYhu_6-S, v=spf1 ip4: 123.123.123.123 include:_spf`
SOA	1	`ns77.domaincontrol.com dns.jomax.net`

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (v0n0.nic.systems, v0n0.nic.systems, v0n2.nic.systems...)

Analysis

IP Addresses

berkeley.systems resolves to just one IP address, 54.161.150.96.

Host names like ec2-54-161-150-96.compute-1.amazonaws.com are further examples that share IP numbers with berkeley.systems.

Name Servers

Two name servers handle the delegation for berkeley.systems: ns77.domaincontrol.com and ns78.domaincontrol.com.

berkeley.systems shares its NS records with other domains, for example rawrit.com, silverblings.com, airracev.com and two others.

ns77.domaincontrol.com and ns78.domaincontrol.com both carry two IP addresses. The A records for ns77.domaincontrol.com are 97.74.108.49 and 2603:5:21c4::31; the A records for ns78.domaincontrol.com are 173.201.76.49 and 2603:5:22c4::31.

Mail Servers

Five mail servers handle berkeley.systems: aspmx2.googlemail.com, aspmx3.googlemail.com, aspmx.l.google.com and two others.

There is at least a partial MX overlap between berkeley.systems and other domains, including cyncitycomics.com, vapetree.com, ns500794.ns500821.ns500821.ns500795.ns500794.ns500821.ns500821.ns500794.ns500821.ns500795.ns500790.ns500795.lustypartnersfinder.com and two others.

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

Host names that have two IP addresses:

aspmx2.googlemail.com resolves to two addresses: 108.177.123.26 and 2800:3f0:4003:c0f::1b.

aspmx3.googlemail.com resolves to two addresses: 172.253.116.26 and 2a00:1450:400b:c02::1b.

aspmx.l.google.com resolves to two addresses: 172.253.62.27 and 2607:f8b0:4004:c19::1b.

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

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

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

aspmx3.googlemail.com along with alt2.aspmx.l.google.com each resolve to 172.253.116.26 IP addresses.