oppwa.com: IP address, DNS records and WHOIS
Live lookup data for oppwa.com: the IP addresses it resolves to, the DNS records it publishes, and its registration details. The data below is fetched when this page is built and refreshed daily.
At a glance
DNS records
A
| 23.3.68.142 | TTL 20 |
| 23.3.68.155 | TTL 20 |
AAAA
| 2a02:26f0:30::216:e473 | TTL 20 |
| 2a02:26f0:30::216:e490 | TTL 20 |
CNAME
No public records of this type are currently published.
MX
| aciworldwide-com.mail.protection.outlook.com | 10 |
NS
| a1-72.akam.net |
| a13-67.akam.net |
| a16-64.akam.net |
| a2-65.akam.net |
| a22-66.akam.net |
| a5-67.akam.net |
TXT
| identrust_validate=nuP5PA8sLqlT1jG8EBLlfj4ouRMdMi24oN4T2a/GmzWb |
| v=spf1 a:smtp06.outboundmail.org a:smtp05.outboundmail.org a:smtp04.outboundmail.org -all |
SOA
- Primary nameserver
- a1-72.akam.net
- Hostmaster
- mbox-payon-ops-vendor-contact@aciworldwide.com
- Serial
- 2020052025
- Refresh
- 3600 s (1 hour)
- Retry
- 900 s (15 minutes)
- Expire
- 1209600 s (14 days)
- Minimum TTL
- 3600 s (1 hour)
CAA
No public records of this type are currently published.
WHOIS registration data
- Registrar
- MarkMonitor Inc.
- Registered
- Sep 22, 2014
- Expires
- Sep 22, 2028
- Last changed
- Aug 11, 2026
- Status
- client delete prohibited, client transfer prohibited, client update prohibited
- Nameservers
- a1-72.akam.net, a13-67.akam.net, a16-64.akam.net, a2-65.akam.net, a22-66.akam.net, a5-67.akam.net
- DNSSEC signed
- Yes
FAQ
oppwa.com currently resolves to 23.3.68.142, 23.3.68.155, 2a02:26f0:30::216:e473, 2a02:26f0:30::216:e490. Large sites often publish several addresses and rotate them, so the list can differ between checks and between locations.
oppwa.com is registered through MarkMonitor Inc.. The registrant's identity is not published in the public registration record — most owners use a privacy service or the data is redacted.
oppwa.com is served by a1-72.akam.net, a13-67.akam.net, a16-64.akam.net, a2-65.akam.net, a22-66.akam.net, a5-67.akam.net. These are the authoritative nameservers that publish its DNS records.
Run a fresh check
Records change. Run the live tools for an up-to-the-minute answer: