thepointsparty.com - dns.ninja
thepointsparty.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=1786731309 | ||||||
Same first word
thepointsparty.com |
DNS History
12 records (8 active, 4 former)
●NSfred.ns.cloudflare.com2026-03-23 → 2026-08-14 · 3 obs
● 2026-03-23 09:53:10
● 2026-08-14 18:33:20
●NSkiki.ns.cloudflare.com2026-03-23 → 2026-08-14 · 3 obs
● 2026-03-23 09:53:10
● 2026-08-14 18:33:20
○NSns-cloud-a1.googledomains.com2020-01-23 → 2020-01-23 · 3 obs
○ 2026-03-23 09:53:10
○ 2026-08-14 18:33:20
○NSns-cloud-a2.googledomains.com2020-01-23 → 2020-01-23 · 3 obs
○ 2026-03-23 09:53:10
○ 2026-08-14 18:33:20
○NSns-cloud-a3.googledomains.com2020-01-23 → 2020-01-23 · 3 obs
○ 2026-03-23 09:53:10
○ 2026-08-14 18:33:20
○NSns-cloud-a4.googledomains.com2020-01-23 → 2020-01-23 · 3 obs
○ 2026-03-23 09:53:10
○ 2026-08-14 18:33:20
●MXalt1.aspmx.l.google.com2020-01-23 → 2026-08-14 · 2 obs
● 2026-08-14 18:33:20
●MXalt2.aspmx.l.google.com2020-01-23 → 2026-08-14 · 2 obs
● 2026-08-14 18:33:20
●MXalt3.aspmx.l.google.com2020-01-23 → 2026-08-14 · 2 obs
● 2026-08-14 18:33:20
●MXalt4.aspmx.l.google.com2020-01-23 → 2026-08-14 · 2 obs
● 2026-08-14 18:33:20
●MXaspmx.l.google.com2020-01-23 → 2026-08-14 · 2 obs
● 2026-08-14 18:33:20
●A198.202.211.12026-03-23 → 2026-08-14 · 2 obs
● 2026-08-14 18:33:20
🔍 DNS Trace
📋 Delegation Chain
| Zone | Nameservers | Glue |
|---|---|---|
| com | a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net... | - |
| thepointsparty.com | fred.ns.cloudflare.com, kiki.ns.cloudflare.com | 12 records |
✅ Authoritative Response
Server:108.162.193.113
NS records: fred.ns.cloudflare.com, kiki.ns.cloudflare.com
🔒 DNSSEC Status
🔐 Secure (DNSSEC validated)
Chain of trust verified from root to domain
⏱️ Timing
Total: 165ms | Queries: -
📄 Records
| Type | Count | Sample Data |
|---|---|---|
| A | 1 | 198.202.211.1 |
| NS | 2 | fred.ns.cloudflare.com, kiki.ns.cloudflare.com |
| MX | 5 | aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)... |
| TXT | 2 | google-site-verification=ytLoO9STL9gXMww, v=spf1 include:_spf.mlsend.com include:_ |
| SOA | 1 | fred.ns.cloudflare.com dns.cloudflare.co |
📌 Glue Records Collected
Total: 12
Out-of-bailiwick: 12 (fred.ns.cloudflare.com, fred.ns.cloudflare.com, fred.ns.cloudflare.com...)
Analysis
IP Addresses
thepointsparty.com directs to one IP number, which is 198.202.211.1.
Among the host names that share IP numbers with thepointsparty.com are ovationincentives.com, odb.agency, limmersoft.com and two others.
Name Servers
thepointsparty.com has two authoritative name servers — fred.ns.cloudflare.com and kiki.ns.cloudflare.com.
thepointsparty.com has the same name server delegation as a number of other domains, such as workstrategies.net, concentratotalaccess.com, myselectmedical.com and two more.
The name servers of thepointsparty.com overlap at least partially with those of other domains — among them morixmist.biz, ilovegroup.com, people-(0x616e616c)ytix.com and two more.
These name servers commonly appear alongside the name servers fatima.ns.cloudflare.com and walt.ns.cloudflare.com.
Host names resolving to 6 IP numbers:
fred.ns.cloudflare.com points to 108.162.193.113, 172.64.33.113, 173.245.59.113 and 3 other IP addresses.
kiki.ns.cloudflare.com points to 108.162.192.180, 172.64.32.180, 173.245.58.180 and 3 other IP addresses.
Mail Servers
Five mail servers handle thepointsparty.com: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.
thepointsparty.com shares at least some of its mail servers with other domains — for example ns500671.ns500731.ns500754.ns500754.ns500742.ns500742.ns500704.ns500688.ns500671.ns500291.ns500678.ns500291.ns500666.ns500291.ns500131.lustychickser.com, ns500765.ns500693.ns500734.ns500734.ns500734.ns500728.ns500734.ns500588.ns500683.ns500693.ns500699.ns500612.ns500612.ns500110.dtrkdll.com, ns500731.ns500742.ns500754.ns500671.ns500742.ns500671.ns500731.ns500742.ns500704.ns500704.ns500688.ns500671.ns500705.ns500291.ns500688.tenderladiesbz.com and two more.
It is common for these mail servers to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and aspmx3.googlemail.com as mail servers.
Hosts with two IP numbers each:
aspmx.l.google.com resolves to 64.233.180.27 and 2607:f8b0:4004:c07::1a.
alt1.aspmx.l.google.com resolves to 192.178.234.26 and 2800:3f0:4003:c14::1a.
alt2.aspmx.l.google.com resolves to 172.253.116.26 and 2a00:1450:400b:c02::1b.
alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.
alt4.aspmx.l.google.com resolves to 172.253.157.27 and 2a00:1450:400c:c23::1a.