`em1.pge.com`

DNSSEC	⚠️ Not signed
A	54.68.100.66^{🇺🇸 Amazon54.68.0.0/15 EC2 PDX Prefix}
		PTR	`ec2-54-68-100-66.us-west-2.compute.amazonaws.com`
A	54.69.164.0^{🇺🇸 Amazon54.68.0.0/15 EC2 PDX Prefix}
A	54.148.21.103^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
A	54.148.46.57^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
A	54.148.47.72^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
A	54.148.75.181^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
A	54.148.99.139^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
A	54.148.120.105^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
NS	`ns0.pge.com` ⭐
		A	131.89.128.12^{🇺🇸 PGENET131.89.0.0/16 ATTN: Enterprise Network Core 300 Lakeside Drive Oakland CA 94612 United States}
			PTR	`ns0.pge.com`
NS	`ns2.pge.com`
		A	131.89.128.13^{🇺🇸 PGENET131.89.0.0/16 ATTN: Enterprise Network Core 300 Lakeside Drive Oakland CA 94612 United States}
			PTR	`ns2.pge.com`
NS	`ns3.pge.com`
		A	130.19.33.68^{🇺🇸 PGENET130.19.0.0/16 ATTN: Enterprise Network Core 300 Lakeside Drive Oakland CA 94612 United States}
			PTR	`ns3.pge.com`
NS	`ns4.pge.com`
		A	130.19.33.69^{🇺🇸 PGENET130.19.0.0/16 ATTN: Enterprise Network Core 300 Lakeside Drive Oakland CA 94612 United States}
			PTR	`ns4.pge.com`
MX	`send01.em1.pge.com` ⭐
		A	54.68.100.66^{🇺🇸 Amazon54.68.0.0/15 EC2 PDX Prefix}
			PTR	`ec2-54-68-100-66.us-west-2.compute.amazonaws.com`
MX	`send02.em1.pge.com` ⭐
		A	54.69.164.0^{🇺🇸 Amazon54.68.0.0/15 EC2 PDX Prefix}
			PTR	`ec2-54-69-164-0.us-west-2.compute.amazonaws.com`
MX	`send03.em1.pge.com` ⭐
		A	54.148.21.103^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
			PTR	`ec2-54-148-21-103.us-west-2.compute.amazonaws.com`
MX	`send04.em1.pge.com` ⭐
		A	54.148.46.57^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
			PTR	`ec2-54-148-46-57.us-west-2.compute.amazonaws.com`
MX	`send05.em1.pge.com` ⭐
		A	54.148.47.72^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
			PTR	`ec2-54-148-47-72.us-west-2.compute.amazonaws.com`
MX	`send06.em1.pge.com` ⭐
		A	54.148.75.181^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
			PTR	`ec2-54-148-75-181.us-west-2.compute.amazonaws.com`
MX	`send07.em1.pge.com` ⭐
		A	54.148.99.139^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
			PTR	`ec2-54-148-99-139.us-west-2.compute.amazonaws.com`
MX	`send08.em1.pge.com` ⭐
		A	54.148.120.105^{🇺🇸 Amazon54.148.0.0/15 EC2 PDX prefix}
			PTR	`ec2-54-148-120-105.us-west-2.compute.amazonaws.com`
TXT	`v=spf1 a -all`
SOA	`ns0.pge.com`ibadmin@pge.com serial=2028

`pge.com`

	DNSSEC	⚠️ Not signed
	A	2600:1408:5400:7::170c:921b^{🇺🇸 AKAMAI-ASN12600:1408:5400::/48 Akamai Technologies}
	A	2600:1408:5400:7::170c:921e^{🇺🇸 AKAMAI-ASN12600:1408:5400::/48 Akamai Technologies}
	A	23.201.31.139^{🇺🇸 AKAMAI-ASN123.201.31.0/24 Akamai Technologies}
	A	23.201.31.179^{🇺🇸 AKAMAI-ASN123.201.31.0/24 Akamai Technologies}
	NS	`ns0.pge.com` ⭐
	NS	`a1-61.akam.net`
	NS	`a11-64.akam.net`
	NS	`a12-65.akam.net`
	NS	`a14-66.akam.net`
	NS	`a24-67.akam.net`
	NS	`a3-64.akam.net`
	MX	`pge.mail.protection.outlook.com` ⭐
	TXT	`cisco-ci-domain-verification=8e39e2cc44a07a2fc8400308123a919edfc953590b4d60a7...`
	TXT	`flexera-domain-verification-ktuprhmrkjoxvqhz`
	TXT	`jamf-site-verification=3tEi918myd7vcJQffwCdDg`
	TXT	`docusign=888fcccf-516d-41b9-924d-2a2f05f17e1d`
	TXT	`apple-domain-verification=bQWKrTFCop0Mxkhj`
	TXT	`adobe-idp-site-verification=a3f04b06ed70e900ccc45c5544ce6872c477b8cb3b86d2088...`
	TXT	`onetrust-domain-verification=728dbeb14c514f71b8896e6437d20054`
	TXT	`atlassian-domain-verification=96jahJq1Kj6GE1cqiQeGbPDlhDBTF1SIFfI9Nk3gy0wtrC1...`
	TXT	`apple-domain-verification=MGCpX0fzWvSjvMiD`
	TXT	`zx7swyvCZZsKoOY3ZZhM0rL7G67VUrr+g22lDCZJ9SIf0zHIWQGjstZ0TqN+ftaQr3noz+qyK5jW7...`
	TXT	`google-site-verification=R9xeEGgiJH9odEizr2WsCfO4sPg67YHuC5DAYJMq-I0`
	TXT	`cisco-ci-domain-verification=64a2a470a10322fe154761104c02a241c60c378419ec262b...`
	TXT	`ktuprhmrkjoxvqhz`
	TXT	`google-site-verification=V9_lGMgZSDZvUgcLJUNxeZDzp9JDK0ObW2tBS6G2qng`
	TXT	`00d6g000000easseao`
	TXT	`9DAB-6ED0-EE7C-6855-E4A2-6221-4A9B-8EBE`
	TXT	`fnd6p42gbuppr676r6djlfp4vj`
	TXT	`flexera-domain-verification-jhamephzjnqtqynd`
	TXT	`google-site-verification=5s7_BJ8zG64HB2VQh43Mwoi7amP9UVOHFSvzWibbfRc`
	TXT	`F9C0-9448-A899-CD73-08E8-1464-8A77-9BC3`
	TXT	`adobe-aem-verification=preview-dev.pge.com/55603/382305/b1ad2d25-ecf3-4c89-a4...`
	TXT	`docusign=7de60584-278d-4ee4-a0d2-61072828f595`
	TXT	`v=spf1 ip4:70.42.227.151/32 ip4:70.42.227.152/32 include:spf.protection.outlo...`
	TXT	`atlassian-domain-verification=SMZxbmG5WaWonXstDqgDBFq2OKiYM7jTbJK3tanqoUVNrPW...`
	TXT	`Dynatrace-site-verification=98abb546-9d7c-4ee3-ba66-93ab91af1932__pkdqvq20h1h...`
	TXT	`zxEMQGcROp3U5W3nPDNRhO3Nea8o8YpvM8LXWxaSUCfABAPdzBjNstb0Xwd0SIOazjuDdcWZBmmWd...`
	TXT	`DC4 - 70.42.227.151 / 70.42.227.152 or _spf-dc4.successfactors.com`
	TXT	`google-gws-recovery-domain-verification=69983151`
	TXT	`ESES6P2TIGY3HQ0IJ3UZ77IYIQPM29ZBJOJB169TX`
	TXT	`webexdomainverification.FGXN=4a807683-c94b-42c2-bb64-1d75f62ee70f`
	TXT	`knowbe4-site-verification=1308e8799a2c9b5a04c23224200b2fad`
	TXT	`dukcmifminlfof9327s3d42nea`
	TXT	`cisco-ci-domain-verification=35bd1562a9617c9aa75d7174baae517dd35c829520fb0456...`
	TXT	`B4AA-B8B0-04D9-CE74-E91F-61DB-3E5B-E455`
	TXT	`onetrust-domain-verification=951664164a85476a8eaf6648f7a533d4`
	TXT	`THISISATXTRECORD`
	TXT	`smartsheet-site-validation=oY4fLTP4tTx0PnAZGj46X9JARyeO_NjD`
	SOA	`ns0.pge.com`ibadmin@pge.com serial=93508

WOT: SAFE (92/100)
rank #9371 globally
rank #4611 in the tld
WOT: SAFE (92/100)
📈 Tranco rank: #15,711

Subdomains

send05.em1.pge.com

send04.em1.pge.com

send08.em1.pge.com

send03.em1.pge.com

send02.em1.pge.com

send01.em1.pge.com

send07.em1.pge.com

send06.em1.pge.com

Same first word

em1.me

em1.jp

em1.ch

em1.pl

em1.nl

em1.net

em1.com

em1.cn

em1.com.br

em1.co

em1.de

em1.fr

em1.no

em1.io

em1.it

em1.ru

em1.ca

em1.eu

em1.cc

Similar names

1me.org

e1m.com

me1.jp

e1m.tv

1me.cz

e1m.net

1me.de

e1m.cn

m1e.com

me1.dk

1me.info

m1e.net

me1.nl

1em.ir

1me.me

1me.com

me1.co.jp

1em.eu

1em.com

1me.in

me1.tv

1em.net

1me.co

me1.co

1me.xyz

1em.cn

me1.fr

me1.com

me1.cn

1em.org

1em.ru

1me.eu

m1e.ru

1em.de

me1.ru

1me.net

m1e.co.uk

me1.ca

me1.ltd

1me.nl

me1.de

me1.in

1me.idv.tw

m1e.ws

1me.club

m1e.org

1me.pl

m1e.com.au

me1.org

e1m.de

e1m.bayern

1me.app

me1.net

DNS History

23 records (20 active, 3 former)

○NScan13.pge.com2018-07-17 → 2018-07-17 · 3 obs

● 2018-07-17 10:56:14
○ 2026-04-21 07:21:16
○ 2026-04-24 04:06:04

○NScan14.pge.com2018-07-17 → 2018-07-17 · 3 obs

● 2018-07-17 10:56:14
○ 2026-04-21 07:21:16
○ 2026-04-24 04:06:04

●NSns0.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●NSns2.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●NSns3.pge.com2026-04-21 → 2026-04-24 · 3 obs

○ 2018-07-17 10:56:14
● 2026-04-21 07:21:16
● 2026-04-24 04:06:04

●NSns4.pge.com2026-04-21 → 2026-04-24 · 3 obs

○ 2018-07-17 10:56:14
● 2026-04-21 07:21:16
● 2026-04-24 04:06:04

○NSns8.pge.com2018-07-17 → 2018-07-17 · 3 obs

● 2018-07-17 10:56:14
○ 2026-04-21 07:21:16
○ 2026-04-24 04:06:04

●MXsend01.em1.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●MXsend02.em1.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●MXsend03.em1.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●MXsend04.em1.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●MXsend05.em1.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●MXsend06.em1.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●MXsend07.em1.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●MXsend08.em1.pge.com2018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●A54.148.120.1052018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●A54.148.21.1032018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●A54.148.46.572018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●A54.148.47.722018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●A54.148.75.1812018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●A54.148.99.1392018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●A54.68.100.662018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

●A54.69.164.02018-07-17 → 2026-04-24 · 2 obs

● 2018-07-17 10:56:14
● 2026-04-24 04:06:04

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	i.gtld-servers.net, m.gtld-servers.net, c.gtld-servers.net, g.gtld-servers.net...	-
pge.com	a3-64.akam.net, a12-65.akam.net, a24-67.akam.net, a11-64.akam.net...	-
em1.pge.com	ns3.pge.com, ns2.pge.com, ns0.pge.com, ns4.pge.com	4 records

✅ Authoritative Response

Server:130.19.33.69

NS records: ns3.pge.com, ns2.pge.com, ns0.pge.com, ns4.pge.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for pge.com (unsigned zone)

⏱️ Timing

Total: 540ms | Queries: -

📄 Records

Type	Count	Sample Data
A	8	`54.148.120.105, 54.148.99.139...`
NS	4	`ns3.pge.com, ns2.pge.com...`
MX	8	`send06.em1.pge.com (pri: 50), send05.em1.pge.com (pri: 50)...`
TXT	1	`v=spf1 a -all`
SOA	1	`ns0.pge.com ibadmin.pge.com`

📌 Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (ns3.pge.com, ns4.pge.com, ns2.pge.com...)

Analysis

Hierarchy

em1.pge.com is the parent of send05.em1.pge.com, send04.em1.pge.com, send08.em1.pge.com, send03.em1.pge.com, send02.em1.pge.com and several other host names.

IP Addresses

Eight IP numbers are pointed to by em1.pge.com: 54.68.100.66, 54.69.164.0, 54.148.21.103, 54.148.46.57, 54.148.47.72, 54.148.75.181, 54.148.99.139 and 54.148.120.105.

Other host names, for instance ec2-54-148-75-181.us-west-2.compute.amazonaws.com, send08.em1.pge.com, send03.em1.pge.com, ec2-54-148-21-103.us-west-2.compute.amazonaws.com and send02.em1.pge.com share IP numbers with em1.pge.com.

Name Servers

em1.pge.com is delegated to four name servers: ns0.pge.com, ns2.pge.com, ns3.pge.com and ns4.pge.com.

em1.pge.com at least partially shares its name servers with other domains, for instance notifications.pge.com, pgecorp.com, 125.68.192.in-addr.arpa, 123.68.192.in-addr.arpa and 121.68.192.in-addr.arpa.

These name servers are commonly used alongside can13.pge.com and can14.pge.com.

Host names with one IP number: ns0.pge.com points to 131.89.128.12; ns2.pge.com points to 131.89.128.13; ns3.pge.com points to 130.19.33.68; ns4.pge.com points to 130.19.33.69.

Mail Servers

Eight mail servers handle em1.pge.com: send01.em1.pge.com, send02.em1.pge.com, send03.em1.pge.com, send04.em1.pge.com, send05.em1.pge.com, send06.em1.pge.com, send07.em1.pge.com and send08.em1.pge.com.

Host names with one IP number:

send01.em1.pge.com points to: 54.68.100.66

send02.em1.pge.com points to: 54.69.164.0

send03.em1.pge.com points to: 54.148.21.103

send04.em1.pge.com points to: 54.148.46.57

send05.em1.pge.com points to: 54.148.47.72

send06.em1.pge.com points to: 54.148.75.181

send07.em1.pge.com points to: 54.148.99.139

send08.em1.pge.com points to: 54.148.120.105

em1.pge.com - robtex.com

em1.pge.com

pge.com

Subdomains

Same first word

Similar names

DNS History

🔍 DNS Trace

📋 Delegation Chain

✅ Authoritative Response

🔒 DNSSEC Status

⏱️ Timing

📄 Records

📌 Glue Records Collected

Analysis

Hierarchy

IP Addresses

Name Servers

Mail Servers

`em1.pge.com`

`pge.com`