opulencephp.com - dns.ninja
opulencephp.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=1785395232 | ||||||
Subdomains
www.opulencephp.com |
Same first word
opulencephp.com |
DNS History
12 records (10 active, 2 former)
●NSns-1372.awsdns-43.org2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●NSns-159.awsdns-19.com2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●NSns-1628.awsdns-11.co.uk2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●NSns-916.awsdns-50.net2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●MXalt1.aspmx.l.google.com2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●MXalt2.aspmx.l.google.com2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●MXalt3.aspmx.l.google.com2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●MXalt4.aspmx.l.google.com2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●MXaspmx.l.google.com2016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
●A45.55.96.682016-12-09 → 2026-07-30 · 2 obs
● 2026-07-30 07:29:26
○PTR45.55.226.952026-02-16 → 2026-02-16 · 4 obs
● 2026-02-16 01:45:00
○ 2026-03-27 07:29:20
○ 2026-07-30 07:29:26
○PTR45.55.226.952016-12-09 → 2026-02-16 · 4 obs
● 2026-02-16 01:45:00
○ 2026-03-27 07:29:20
○ 2026-07-30 07:29:26
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, j.gtld-servers.net, d.gtld-servers.net, l.gtld-servers.net... | - |
| opulencephp.com | ns-159.awsdns-19.com, ns-916.awsdns-50.net, ns-1628.awsdns-11.co.uk, ns-1372.awsdns-43.org | 2 records |
✅ Authoritative Response
Server:205.251.192.159
NS records: ns-159.awsdns-19.com, ns-916.awsdns-50.net, ns-1628.awsdns-11.co.uk, ns-1372.awsdns-43.org
🔒 DNSSEC Status
⚠️ Insecure (no DNSSEC)
No DS record for opulencephp.com (unsigned zone)
⏱️ Timing
Total: 306ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 45.55.96.68 |
| NS | 4 | ns-1372.awsdns-43.org, ns-159.awsdns-19.com... |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 1 | v=spf1 include:_spf.google.com ~all |
| SOA | 1 | ns-1628.awsdns-11.co.uk awsdns-hostmaste |
📌 Glue Records Collected
Total: 2
Out-of-bailiwick: 2 (ns-159.awsdns-19.com, ns-159.awsdns-19.com)
Analysis
Hierarchy
The domain www.opulencephp.com falls under the parent opulencephp.com.
IP Addresses
opulencephp.com resolves to one IP address: 45.55.96.68.
www.opulencephp.com, for instance, is one of the other host names sharing IP numbers with opulencephp.com.
Name Servers
The authoritative name servers for opulencephp.com are ns-159.awsdns-19.com, ns-916.awsdns-50.net, ns-1372.awsdns-43.org and ns-1628.awsdns-11.co.uk.
At least some of opulencephp.com's name servers are shared with other domains, for example 6.177.35.in-addr.arpa, 25.41.13.in-addr.arpa, aithauwhosaign.com and two more.
These name servers tend to co-occur with ns1-24-eu-west-2.ec2-rdns.amazonaws.com, ns2-24-eu-west-2.ec2-rdns.amazonaws.com, ns3-24-eu-west-2.ec2-rdns.amazonaws.com and 5 other name servers in the same DNS delegations.
Four hostnames, each resolving to a pair of IP addresses: ns-159.awsdns-19.com directs to 205.251.192.159 and 2600:9000:5300:9f00::1; ns-916.awsdns-50.net directs to 205.251.195.148 and 2600:9000:5303:9400::1; ns-1372.awsdns-43.org directs to 205.251.197.92 and 2600:9000:5305:5c00::1; ns-1628.awsdns-11.co.uk directs to 205.251.198.92 and 2600:9000:5306:5c00::1.
Mail Servers
Five mail servers handle opulencephp.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
opulencephp.com has at least partial mail server overlap with other domains such as ns500759.ns500698.ns500758.ns500758.ns500698.ns500698.ns500698.ns500736.ns500736.ns500698.ns500698.ns500708.ns500708.ns500652.ns500652.ns500576.trackreceptor.com, ns500742.ns500754.ns500742.ns500704.ns500704.ns500704.ns500705.ns500649.ns500671.ns500142.lusty(0x736c7574)z.com, ns500758.ns500698.ns500759.ns500758.ns500758.ns500759.ns500736.ns500735.ns500698.ns500576.ns500708.ns500708.ns500619.ns500698.trackreceptor.com 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 directs traffic to 172.253.122.26 and 2607:f8b0:4004:c23::1a.
alt1.aspmx.l.google.com directs traffic to 108.177.123.26 and 2800:3f0:4003:c0f::1a.
alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com directs traffic to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1a.