cpftoken.com - dns.ninja

cpftoken.com

DNSSEC⚠️ Not signed
A72.167.37.48πŸ‡ΊπŸ‡Έ AS39810172.167.32.0/20 GoDaddy.com, LLC
PTR48.37.167.72.host.secureserver.net
NSns1.adsys.digital ⭐
A72.167.37.48πŸ‡ΊπŸ‡Έ AS39810172.167.32.0/20 GoDaddy.com, LLC
PTR48.37.167.72.host.secureserver.net
NSns2.adsys.digital
A72.167.35.109πŸ‡ΊπŸ‡Έ AS39810172.167.32.0/20 GoDaddy.com, LLC
PTR109.35.167.72.host.secureserver.net
MXcpftoken.com ⭐
A72.167.37.48πŸ‡ΊπŸ‡Έ AS39810172.167.32.0/20 GoDaddy.com, LLC
PTR48.37.167.72.host.secureserver.net
TXTv=spf1 +a +mx +ip4:72.167.37.48 ~all
SOAns1.adsys.digitalroot@julius.adsys.digital 2026-06-24 #1

com

MX for

Same first word

Similar names

DNS History

9 records (4 active, 5 former)

20192020202120222023202420252026NSns1.adsys.digitalns2.adsys.digitalns-1043.awsdns-02.orgns-1603.awsdns-08.co.ukns-22.awsdns-02.comns-585.awsdns-09.netMXcpftoken.comA72.167.37.4834.235.86.20
β—‹NSns-1043.awsdns-02.org2018-05-11 β†’ 2018-05-11 Β· 4 obs
● 2018-05-11 20:10:14
● 2018-05-11 20:10:34
β—‹ 2026-03-23 13:45:32
β—‹ 2026-08-09 09:10:40
β—‹NSns-1603.awsdns-08.co.uk2018-05-11 β†’ 2018-05-11 Β· 4 obs
● 2018-05-11 20:10:14
● 2018-05-11 20:10:34
β—‹ 2026-03-23 13:45:32
β—‹ 2026-08-09 09:10:40
β—‹NSns-22.awsdns-02.com2018-05-11 β†’ 2018-05-11 Β· 4 obs
● 2018-05-11 20:10:14
● 2018-05-11 20:10:34
β—‹ 2026-03-23 13:45:32
β—‹ 2026-08-09 09:10:40
β—‹NSns-585.awsdns-09.net2018-05-11 β†’ 2018-05-11 Β· 4 obs
● 2018-05-11 20:10:14
● 2018-05-11 20:10:34
β—‹ 2026-03-23 13:45:32
β—‹ 2026-08-09 09:10:40
●NSns1.adsys.digital2026-03-23 β†’ 2026-08-09 Β· 3 obs
β—‹ 2018-05-11 20:10:34
● 2026-03-23 13:45:32
● 2026-08-09 09:10:40
●NSns2.adsys.digital2026-03-23 β†’ 2026-08-09 Β· 3 obs
β—‹ 2018-05-11 20:10:34
● 2026-03-23 13:45:32
● 2026-08-09 09:10:40
●MXcpftoken.com2026-03-23 β†’ 2026-08-09 Β· 2 obs
● 2026-03-23 13:45:32
● 2026-08-09 09:10:40
β—‹A34.235.86.202018-05-11 β†’ 2018-05-11 Β· 4 obs
● 2018-05-11 20:10:14
● 2018-05-11 20:10:34
β—‹ 2026-03-23 13:45:32
β—‹ 2026-08-09 09:10:40
●A72.167.37.482026-03-23 β†’ 2026-08-09 Β· 3 obs
β—‹ 2018-05-11 20:10:34
● 2026-03-23 13:45:32
● 2026-08-09 09:10:40

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coma.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...-
cpftoken.comns1.adsys.digital, ns2.adsys.digital-

βœ… Authoritative Response

Server:72.167.35.109

NS records: ns1.adsys.digital, ns2.adsys.digital

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for cpftoken.com (unsigned zone)

⏱️ Timing

Total: 514ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A172.167.37.48
NS2ns2.adsys.digital, ns1.adsys.digital
MX1cpftoken.com (pri: 0)
TXT1v=spf1 +a +mx +ip4:72.167.37.48 ~all
SOA1ns1.adsys.digital root.julius.adsys.digi

Analysis

Mail Server Role

cpftoken.com is listed as a mail server for itself.

IP Addresses

cpftoken.com resolves to one IP address: 72.167.37.48.

hellobox.com.br, biocarb.com.br, fitbox.com.br and two other host names share IP numbers with cpftoken.com.

Name Servers

cpftoken.com uses two name servers for its delegation: ns1.adsys.digital and ns2.adsys.digital.

cpftoken.com uses the same name servers as several other domains β€” among them adsys.com.br, agrofortte.com.br, agenciadivulgue.com.br and two more.

Some name servers delegated to cpftoken.com are also used by other domains, notably fitbox.com.br and adsys.digital.

The name servers ns1.72-167-37-48.cprapid.com, ns2.72-167-37-48.cprapid.com and julius.adsys.digital are often found in combination with these name servers.

ns1.adsys.digital β†’ 72.167.37.48 and ns2.adsys.digital β†’ 72.167.35.109: one IP number per host name.

Mail Servers

Mail for cpftoken.com is handled by one mail server β€” cpftoken.com.

cpftoken.com directs to just one IP number, 72.167.37.48.