wapmo.com - dns.ninja

`wapmo.com`

DNSSEC	⚠️ Not signed
A	44.232.173.249^{🇺🇸 Amazon44.224.0.0/11 EC2 PDX prefix}
		PTR	`ec2-44-232-173-249.us-west-2.compute.amazonaws.com`
A	52.40.42.113^{🇺🇸 Amazon52.40.0.0/14 EC2 PDX prefix}
NS	`launch1.spaceship.net` ⭐
		A	2400:cb00:2049:1::a29f:1a26^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.38^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`launch2.spaceship.net`
		A	2400:cb00:2049:1::a29f:1b20^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.27.32^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`verification-3rbfeg9abp4wvhc7lqry39.ns101.verify.hn` ⚠️ Not in zone NS records
		A	13.248.169.48^{🇺🇸 Amazon13.248.160.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
		A	76.223.54.146^{🇺🇸 Amazon76.223.48.0/20}
			PTR	`a904c694c05102f30.awsglobalaccelerator.com`
TXT	`7a2ab70f-73b1-4089-8ae8-39ca9a2083ed`
SOA	`launch1.spaceship.net`support@spaceship.com serial=1778165572

`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.net`nstld@verisign-grs.com serial=1783228766

Same first word

wapmo.com

Similar names

wampo.com

wmpoa.com

mopaw.com

powma.com

woamp.com

pomwa.tk

mpowa.co.za

wmapo.org

waopm.com

womap.com

wmpoa.net

mapow.co

wampo.de

mapwo.com

mpowa.mobi

wmapo.com

mwopa.com

wpmao.com

mowpa.org

mwapo.com

ompaw.com

wompa.top

mpowa.com

wpoam.com

mpowa.org

apomw.com

wampo.net

ampow.com

wampo.org

omwpa.com

mwpoa.com

mowap.s3.ap-south-1.amazonaws.com

maowp.org

wapom.com

womap.com.cn

mapow.com

mawop.org

mwpoa.org

apwom.org

mapwo.org.af

DNS History

14 records (5 active, 9 former)

○NS(root)2015-08-02 → 2017-09-09 · 4 obs

● 2015-08-02 12:52:14
● 2017-09-09 03:01:36
○ 2026-02-15 19:08:20
○ 2026-07-05 05:37:08

●NSlaunch1.spaceship.net2026-02-18 → 2026-07-05 · 3 obs

○ 2026-02-15 19:08:20
● 2026-02-18 16:44:24
● 2026-07-05 05:37:08

●NSlaunch2.spaceship.net2026-02-18 → 2026-07-05 · 3 obs

○ 2026-02-15 19:08:20
● 2026-02-18 16:44:24
● 2026-07-05 05:37:08

○NSns1.afternic.com2026-02-15 → 2026-02-15 · 4 obs

○ 2017-09-09 03:01:36
● 2026-02-15 19:08:20
○ 2026-02-18 16:44:24
○ 2026-07-05 05:37:08

○NSns2.afternic.com2026-02-15 → 2026-02-15 · 4 obs

○ 2017-09-09 03:01:36
● 2026-02-15 19:08:20
○ 2026-02-18 16:44:24
○ 2026-07-05 05:37:08

●NSverification-3rbfeg9abp4wvhc7lqry39.ns101.verify.hn2026-02-15 → 2026-07-05 · 6 obs

○ 2017-09-09 03:01:36
● 2026-02-15 19:08:20
● 2026-06-01 22:02:00
○ 2026-06-05 23:43:44
● 2026-06-10 04:55:10
● 2026-07-05 05:37:08

○MXmx.ym.163.com2015-11-21 → 2016-04-20 · 4 obs

● 2015-11-21 22:36:14
● 2016-04-20 09:31:42
○ 2017-03-31 20:56:42
○ 2026-07-05 05:37:08

○MXmxdomain.qq.com2017-03-31 → 2017-03-31 · 4 obs

○ 2016-04-20 09:31:42
● 2017-03-31 20:56:42
○ 2017-09-05 09:59:12
○ 2026-07-05 05:37:08

○A13.248.169.482026-02-15 → 2026-02-15 · 4 obs

○ 2017-09-05 09:59:12
● 2026-02-15 19:08:20
○ 2026-02-18 16:44:24
○ 2026-07-05 05:37:08

○A198.71.161.532015-08-02 → 2017-03-31 · 4 obs

● 2015-08-02 12:52:14
● 2017-03-31 20:56:42
○ 2017-09-05 09:59:12
○ 2026-07-05 05:37:08

●A44.232.173.2492026-02-18 → 2026-07-05 · 9 obs

○ 2026-02-15 19:08:20
● 2026-02-18 16:44:24
● 2026-03-27 04:48:52
○ 2026-04-06 15:45:46
● 2026-04-10 19:29:24
● 2026-05-19 21:59:30
○ 2026-05-22 03:40:08
● 2026-05-25 15:15:10
● 2026-07-05 05:37:08

●A52.40.42.1132026-02-18 → 2026-07-05 · 9 obs

○A76.223.54.1462026-02-15 → 2026-02-15 · 4 obs

○ 2017-09-05 09:59:12
● 2026-02-15 19:08:20
○ 2026-02-18 16:44:24
○ 2026-07-05 05:37:08

○CNAMEzxt.org2015-08-02 → 2026-02-15 · 4 obs

● 2015-08-02 12:52:14
● 2026-02-15 19:08:20
○ 2026-02-18 16:44:24
○ 2026-07-05 05:37:08

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	e.gtld-servers.net, c.gtld-servers.net, h.gtld-servers.net, i.gtld-servers.net...	-
wapmo.com	launch2.spaceship.net, launch1.spaceship.net, verification-3rbfeg9abp4wvhc7lqry39.ns101.verify.hn	-

✅ Authoritative Response

Server:162.159.26.38

NS records: launch2.spaceship.net, launch1.spaceship.net, verification-3rbfeg9abp4wvhc7lqry39.ns101.verify.hn

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for wapmo.com (unsigned zone)

⏱️ Timing

Total: 3304ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`52.40.42.113, 44.232.173.249`
NS	2	`launch2.spaceship.net, launch1.spaceship.net`
TXT	1	`7a2ab70f-73b1-4089-8ae8-39ca9a2083ed`
SOA	1	`launch1.spaceship.net support.spaceship.`

Analysis

IP Addresses

wapmo.com directs to two IP numbers, 44.232.173.249 and 52.40.42.113

Among the host names that share IP numbers with wapmo.com are where.today, radharaman.com, opservant.com and two others.

Name Servers

wapmo.com has three name servers — launch1.spaceship.net, launch2.spaceship.net and verification-3rbfeg9abp4wvhc7lqry39.ns101.verify.hn.

wapmo.com partially shares its NS delegation with several other domains, including byleng.com, bmctraining.com, thepersonacode.com and two others.

These name servers are regularly seen alongside ns1.afternic.com and ns2.afternic.com as name servers.

Each of launch1.spaceship.net, launch2.spaceship.net and verification-3rbfeg9abp4wvhc7lqry39.ns101.verify.hn points to two IP numbers. launch1.spaceship.net points to 162.159.26.38 and 2400:cb00:2049:1::a29f:1a26. launch2.spaceship.net points to 162.159.27.32 and 2400:cb00:2049:1::a29f:1b20. verification-3rbfeg9abp4wvhc7lqry39.ns101.verify.hn points to 13.248.169.48 and 76.223.54.146.