whowas.com - robtex.com

whowas.com

DNSSEC⚠️ Not signed
A2001:19f0:ac00:3f91:5400:4ff:fe92:5127πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ac00::/38 Vultr Assigned Prefix
PTRwhowas.wpmudev.host
A144.202.105.77πŸ‡ΊπŸ‡Έ AS-VULTR144.202.96.0/20 Vultr Assigned Prefix
NSns1.vultr.com ⭐
A2001:19f0:ccc::1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccc::/48 DNS1
A2001:19f0:ccd::1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96πŸ‡ΊπŸ‡Έ AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
NSns1.wpdns.host
A2001:19f0:ccd::1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96πŸ‡ΊπŸ‡Έ AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
NSns2.wpdns.host
A2001:19f0:ccd::2πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns2.vultr.com
A173.199.96.97πŸ‡ΊπŸ‡Έ AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns2.vultrusercontent.com
NSns3.wpdns.host
A2001:19f0:ccd::1πŸ‡ΊπŸ‡Έ AS-VULTR2001:19f0:ccd::/48 Vultr Assigned Prefix
PTRns1.vultr.com
A173.199.96.96πŸ‡ΊπŸ‡Έ AS-VULTR173.199.96.0/24 Vultr Assigned Prefix
PTRns1.vultrusercontent.com
MXmx.whowas.com.cust.b.hostedemail.com ⭐
A64.98.38.4πŸ‡¨πŸ‡¦ TUCOWS-364.98.38.0/24 IPv4 Allow
PTRmx.b.hostedemail.com
TXTv=spf1 include:_spf.hostedemail.com ~all
TXTopenai-domain-verification=dv-9tI0l6ZL5yJuxHTqVJImaEJg
SOAns1.vultr.comdnsadm@choopa.com serial=0

com

Same first word

Similar names

DNS History

16 records (7 active, 9 former)

2008201020122014201620182020202220242026NSns1.vultr.comns1.wpdns.hostns2.wpdns.hostns3.wpdns.hostns3.secureserver.netns4.secureserver.netns41.domaincontrol.comns42.domaincontrol.comMXmx.whowas.com.cust.b.hostedemail.commailstore1.secureserver.netsmtp.secureserver.netA144.202.105.772001:19f0:ac00:3f91:5400:4ff:fe92:512750.62.219.150.62.219.12868.178.211.88
●NSns1.vultr.com2026-03-28 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-05 17:51:16
● 2026-03-28 05:05:18
● 2026-03-28 05:05:20
●NSns1.wpdns.host2026-03-28 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-05 17:51:16
● 2026-03-28 05:05:18
● 2026-03-28 05:05:20
●NSns2.wpdns.host2026-03-28 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-05 17:51:16
● 2026-03-28 05:05:18
● 2026-03-28 05:05:20
β—‹NSns3.secureserver.net2017-04-05 β†’ 2017-04-05 Β· 4 obs
β—‹ 2007-10-29 05:45:12
● 2017-04-05 17:51:16
β—‹ 2026-03-28 05:05:18
β—‹ 2026-03-28 05:05:20
●NSns3.wpdns.host2026-03-28 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-05 17:51:16
● 2026-03-28 05:05:18
● 2026-03-28 05:05:20
β—‹NSns4.secureserver.net2017-04-05 β†’ 2017-04-05 Β· 4 obs
β—‹ 2007-10-29 05:45:12
● 2017-04-05 17:51:16
β—‹ 2026-03-28 05:05:18
β—‹ 2026-03-28 05:05:20
β—‹NSns41.domaincontrol.com2007-10-29 β†’ 2017-04-05 Β· 4 obs
● 2007-10-29 05:45:12
● 2017-04-05 17:51:16
β—‹ 2026-03-28 05:05:18
β—‹ 2026-03-28 05:05:20
β—‹NSns42.domaincontrol.com2007-10-29 β†’ 2017-04-05 Β· 4 obs
● 2007-10-29 05:45:12
● 2017-04-05 17:51:16
β—‹ 2026-03-28 05:05:18
β—‹ 2026-03-28 05:05:20
β—‹MXmailstore1.secureserver.net2007-10-29 β†’ 2017-04-05 Β· 4 obs
● 2007-10-29 05:45:12
● 2017-04-05 17:51:16
β—‹ 2026-03-28 05:05:18
β—‹ 2026-03-28 05:05:20
●MXmx.whowas.com.cust.b.hostedemail.com2026-03-28 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-05 17:51:16
● 2026-03-28 05:05:18
● 2026-03-28 05:05:20
β—‹MXsmtp.secureserver.net2007-10-29 β†’ 2017-04-05 Β· 4 obs
● 2007-10-29 05:45:12
● 2017-04-05 17:51:16
β—‹ 2026-03-28 05:05:18
β—‹ 2026-03-28 05:05:20
●A144.202.105.772026-03-28 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-05 17:51:16
● 2026-03-28 05:05:18
● 2026-03-28 05:05:20
●A2001:19f0:ac00:3f91:5400:4ff:fe92:51272026-03-28 β†’ 2026-03-28 Β· 3 obs
β—‹ 2017-04-05 17:51:16
● 2026-03-28 05:05:18
● 2026-03-28 05:05:20
β—‹A50.62.219.12015-05-29 β†’ 2015-09-19 Β· 5 obs
β—‹ 2007-10-29 05:45:12
● 2015-05-29 16:08:04
● 2015-09-19 04:52:02
β—‹ 2015-12-15 23:38:44
β—‹ 2026-03-28 05:05:20
β—‹A50.62.219.1282015-12-15 β†’ 2017-04-05 Β· 5 obs
β—‹ 2015-09-19 04:52:02
● 2015-12-15 23:38:44
● 2017-04-05 17:51:16
β—‹ 2026-03-28 05:05:18
β—‹ 2026-03-28 05:05:20
β—‹A68.178.211.882007-10-29 β†’ 2007-10-29 Β· 3 obs
● 2007-10-29 05:45:12
β—‹ 2015-05-29 16:08:04
β—‹ 2026-03-28 05:05:20

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
coml.gtld-servers.net, j.gtld-servers.net, h.gtld-servers.net, d.gtld-servers.net...-
whowas.comns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host-

βœ… Authoritative Response

Server:173.199.96.96

NS records: ns1.wpdns.host, ns2.wpdns.host, ns3.wpdns.host

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for whowas.com (unsigned zone)

⏱️ Timing

Total: 195ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A1144.202.105.77
AAAA12001:19f0:ac00:3f91:5400:4ff:fe92:5127
NS3ns1.wpdns.host, ns2.wpdns.host...
MX1mx.whowas.com.cust.b.hostedemail.com (pr
TXT2v=spf1 include:_spf.hostedemail.com ~all, openai-domain-verification=dv-9tI0l6ZL5y
SOA1ns1.vultr.com dnsadm.choopa.com

Analysis

IP Addresses

whowas.com points to two IP numbers: 2001:19f0:ac00:3f91:5400:4ff:fe92:5127 and 144.202.105.77.

Other host names, for instance whowas.wpmudev.host share IP numbers with whowas.com.

Name Servers

whowas.com is delegated to four name servers: ns1.vultr.com, ns1.wpdns.host, ns2.wpdns.host and ns3.wpdns.host.

whowas.com at least partially shares name servers with other domains, for instance premii.com, db9.net, rendellcenter.org, olah.world and alexjaffe.com.

these name servers are often used in conjunction with the name servers ns2.vultr.com.

Hostnames with three IPs:

ns1.vultr.com points to 2001:19f0:ccc::1, 2001:19f0:ccd::1 and 173.199.96.96.

Hostnames with two IPs:

ns1.wpdns.host points to 2001:19f0:ccd::1 and 173.199.96.96.

ns2.wpdns.host points to 2001:19f0:ccd::2 and 173.199.96.97.

ns3.wpdns.host points to 2001:19f0:ccd::1 and 173.199.96.96.

Hostnames that point to 2001:19f0:ccd::1: ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host.

Hostnames that point to 173.199.96.96: ns1.vultr.com, ns1.wpdns.host and ns3.wpdns.host.

Mail Servers

whowas.com is handled by a single mail server, mx.whowas.com.cust.b.hostedemail.com.

mx.whowas.com.cust.b.hostedemail.com points to a single IP: 64.98.38.4.