aawashing.com - robtex.com

aawashing.com

DNSSEC⚠️ Not signed
A2001:19f0:5c00:276e:5400:4ff:fe9d:2b63🇺🇸 AS-VULTR2001:19f0:5c00::/38 Vultr Assigned Prefix
A144.202.49.44🇺🇸 AS-VULTR144.202.48.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
SOAns1.vultr.comdnsadm@choopa.com serial=0

com

DNSSEC🔒 Signed (DS record present)
NSa.gtld-servers.net ⭐
NSb.gtld-servers.net
NSc.gtld-servers.net
NSd.gtld-servers.net
NSe.gtld-servers.net
NSf.gtld-servers.net
NSg.gtld-servers.net
NSh.gtld-servers.net
NSi.gtld-servers.net
NSj.gtld-servers.net
NSk.gtld-servers.net
NSl.gtld-servers.net
NSm.gtld-servers.net
SOAa.gtld-servers.netnstld@verisign-grs.com serial=1775966497

Same first word

aawashing.com
aawashing.tempurl.host

Similar names

shinagawa.org
shinagawa.biz
shinagawa.com
shinagawa.co.jp
shinagawa.ph
shinagawa.or.jp
ashaiwang.com

DNS History

16 records (6 active, 10 former)

2020202120222023202420252026NSns1.vultr.comns1.wpdns.hostns2.wpdns.hostns3.wpdns.hostdns097.b.register.comdns162.a.register.comdns176.d.register.comdns238.c.register.comMXalt1.aspmx.l.google.comalt2.aspmx.l.google.comalt3.aspmx.l.google.comalt4.aspmx.l.google.comaspmx.l.google.comA144.202.49.442001:19f0:5c00:276e:5400:4ff:fe9d:2b63199.34.228.164
○NSdns097.b.register.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
○NSdns162.a.register.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
○NSdns176.d.register.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
○NSdns238.c.register.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
●NSns1.vultr.com2026-04-09 → 2026-04-12 · 3 obs
○ 2019-12-18 15:21:24
● 2026-04-09 01:58:50
● 2026-04-12 04:24:14
●NSns1.wpdns.host2026-04-09 → 2026-04-12 · 3 obs
○ 2019-12-18 15:21:24
● 2026-04-09 01:58:50
● 2026-04-12 04:24:14
●NSns2.wpdns.host2026-04-09 → 2026-04-12 · 3 obs
○ 2019-12-18 15:21:24
● 2026-04-09 01:58:50
● 2026-04-12 04:24:14
●NSns3.wpdns.host2026-04-09 → 2026-04-12 · 3 obs
○ 2019-12-18 15:21:24
● 2026-04-09 01:58:50
● 2026-04-12 04:24:14
○MXalt1.aspmx.l.google.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
○MXalt2.aspmx.l.google.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
○MXalt3.aspmx.l.google.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
○MXalt4.aspmx.l.google.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
○MXaspmx.l.google.com2019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
●A144.202.49.442026-04-09 → 2026-04-12 · 3 obs
○ 2019-12-18 15:21:24
● 2026-04-09 01:58:50
● 2026-04-12 04:24:14
○A199.34.228.1642019-12-18 → 2019-12-18 · 3 obs
● 2019-12-18 15:21:24
○ 2026-04-09 01:58:50
○ 2026-04-12 04:24:14
●A2001:19f0:5c00:276e:5400:4ff:fe9d:2b632026-04-09 → 2026-04-12 · 3 obs
○ 2019-12-18 15:21:24
● 2026-04-09 01:58:50
● 2026-04-12 04:24:14

🔍 DNS Trace

📋 Delegation Chain

ZoneNameserversGlue
comf.gtld-servers.net, g.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net...-
aawashing.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 aawashing.com (unsigned zone)

⏱️ Timing

Total: 430ms | Queries: -

📄 Records

TypeCountSample Data
A1144.202.49.44
AAAA12001:19f0:5c00:276e:5400:4ff:fe9d:2b63
NS3ns2.wpdns.host, ns3.wpdns.host...
SOA1ns1.vultr.com dnsadm.choopa.com

Analysis

IP Addresses

The entity aawashing.com points to two IP numbers: 2001:19f0:5c00:276e:5400:4ff:fe9d:2b63 and 144.202.49.44.

Other host names, for instance, aawashing.tempurl.host share IP numbers with aawashing.com.

Name Servers

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

aawashing.com shares name servers with other domains at least partially, for example aocrecs.com, jpsmproductions.de, keteringdukat.com, hanaq.ec and magicvoip.net.

These name servers are commonly used with ns2.vultr.com.

Host names with three IP numbers:

The host name ns1.vultr.com points to 2001:19f0:ccc::12001:19f0:ccd::1 and 173.199.96.96.

Host names with two IP numbers:

The host name ns1.wpdns.host points to 2001:19f0:ccd::1 and 173.199.96.96; the host name ns2.wpdns.host points to 2001:19f0:ccd::2 and 173.199.96.97; the host name ns3.wpdns.host points to 2001:19f0:ccd::1 and 173.199.96.96.

Host names that point to 2001:19f0:ccd::1: ns1.vultr.comns1.wpdns.host and ns3.wpdns.host.

Host names that point to 173.199.96.96: ns1.vultr.comns1.wpdns.host and ns3.wpdns.host.