picower.com - dns.ninja
picower.com
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.netnstld@verisign-grs.com serial=1784516312 | ||||||
Same first word
picower.com |
Similar names
DNS History
8 records (6 active, 2 former)
●NSns-1357.awsdns-41.org2015-06-06 → 2026-07-20 · 2 obs
● 2026-07-20 03:14:40
●NSns-1738.awsdns-25.co.uk2015-06-06 → 2026-07-20 · 2 obs
● 2026-07-20 03:14:40
●NSns-25.awsdns-03.com2015-06-06 → 2026-07-20 · 2 obs
● 2026-07-20 03:14:40
●NSns-962.awsdns-56.net2015-06-06 → 2026-07-20 · 2 obs
● 2026-07-20 03:14:40
○MXpicower.com.inbound10.mxlogic.net2015-06-06 → 2016-01-19 · 4 obs
● 2016-01-19 21:56:44
○ 2016-06-25 18:40:16
○ 2026-07-20 03:14:40
○MXpicower.com.inbound10.mxlogicmx.net2015-06-06 → 2016-01-19 · 4 obs
● 2016-01-19 21:56:44
○ 2016-06-25 18:40:16
○ 2026-07-20 03:14:40
●MXus-smtp-inbound-1.mimecast.com2016-06-25 → 2026-07-20 · 3 obs
● 2016-06-25 18:40:16
● 2026-07-20 03:14:40
●MXus-smtp-inbound-2.mimecast.com2016-06-25 → 2026-07-20 · 3 obs
● 2016-06-25 18:40:16
● 2026-07-20 03:14:40
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | b.gtld-servers.net, j.gtld-servers.net, i.gtld-servers.net, e.gtld-servers.net... | - |
| picower.com | ns-25.awsdns-03.com, ns-962.awsdns-56.net, ns-1738.awsdns-25.co.uk, ns-1357.awsdns-41.org | 2 records |
✅ Authoritative Response
Server:205.251.197.77
NS records: ns-25.awsdns-03.com, ns-962.awsdns-56.net, ns-1738.awsdns-25.co.uk, ns-1357.awsdns-41.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for picower.com (unsigned zone)
⏱️ Timing
Total: 615ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| NS | 4 | ns-1357.awsdns-41.org, ns-1738.awsdns-25.co.uk... |
| MX | 2 | us-smtp-inbound-1.mimecast.com (pri: 0), us-smtp-inbound-2.mimecast.com (pri: 0) |
| TXT | 6 | 1DVD52nC4NsJzALQ2B4samyhxRAd6ouIXkwDYqZy, MS=ms76287337... |
| SOA | 1 | ns-25.awsdns-03.com awsdns-hostmaster.am |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-25.awsdns-03.com, ns-25.awsdns-03.com)
Analysis
Name Servers
The authoritative name servers for picower.com are ns-25.awsdns-03.com, ns-962.awsdns-56.net, ns-1357.awsdns-41.org and ns-1738.awsdns-25.co.uk.
picower.com has at least partial name server overlap with other domains, such as leadingedgemail.com, vive-unique.com, d5oojzteh1rf3.cloudfront.net and two others.
These name servers tend to appear together with the name servers ns-451.awsdns-56.com, ns-538.awsdns-03.net and ns-1306.awsdns-35.org.
ns-25.awsdns-03.com, ns-962.awsdns-56.net, ns-1357.awsdns-41.org and ns-1738.awsdns-25.co.uk all point to exactly two IP numbers each: ns-25.awsdns-03.com → 205.251.192.25 and 2600:9000:5300:1900::1; ns-962.awsdns-56.net → 205.251.195.194 and 2600:9000:5303:c200::1; ns-1357.awsdns-41.org → 205.251.197.77 and 2600:9000:5305:4d00::1; ns-1738.awsdns-25.co.uk → 205.251.198.202 and 2600:9000:5306:ca00::1.
Mail Servers
Mail for picower.com is handled by two mail servers — us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.com.
picower.com uses an identical mail server configuration to several other domains — among them matzka.com, ohiobasketball.com, libertyins.com and two more.
picower.com has mail servers in common with other domains — for example imd.idaho.gov and business.idaho.gov.
Hostnames that resolve to 6 IP addresses:
Hostname us-smtp-inbound-1.mimecast.com directs to 170.10.128.141, 170.10.128.221 and 170.10.128.242 along with 3 other IP addresses.
Hostname us-smtp-inbound-2.mimecast.com directs to 170.10.128.141, 170.10.128.221 and 170.10.128.242 along with 3 other IP addresses.
Both us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.com resolve to 170.10.128.141 IP addresses each.
Both us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.com resolve to 170.10.128.221 IP addresses each.
Both us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.com resolve to 170.10.128.242 IP addresses each.
Both us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.com resolve to 170.10.132.141 IP addresses each.
Both us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.com resolve to 170.10.132.221 IP addresses each.
Both us-smtp-inbound-1.mimecast.com and us-smtp-inbound-2.mimecast.com resolve to 170.10.132.242 IP addresses each.