fwave.com - dns.ninja

`fwave.com`

DNSSEC	⚠️ Not signed
A	2606:4700:3031::6815:2576^{🇺🇸 Cloudflare2606:4700:3031::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	2606:4700:3037::ac43:cfd7^{🇺🇸 Cloudflare2606:4700:3037::/48 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	104.21.37.118^{Cloudflare104.21.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
A	172.67.207.215^{🇺🇸 Cloudflare172.67.192.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US} ✓ In HTTPS hints
NS	`rick.ns.cloudflare.com` ⭐
		A	2606:4700:58::adf5:3b8b^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c18b^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`rick.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:218b^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`rick.ns.cloudflare.com`
		A	108.162.193.139^{🇺🇸 Cloudflare108.162.193.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	172.64.33.139^{🇺🇸 Cloudflare172.64.33.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
		A	173.245.59.139^{🇺🇸 Cloudflare173.245.59.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`rick.ns.cloudflare.com`
NS	`zariyah.ns.cloudflare.com`
		A	2606:4700:50::a29f:2648^{🇺🇸 Cloudflare2606:4700:50::/44 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zariyah.ns.cloudflare.com`
		A	2803:f800:50::6ca2:c248^{🇨🇷 Cloudflare2803:f800:50::/45 LACNIC generated route6 for CloudFlare Latin America S.R.L}
			PTR	`zariyah.ns.cloudflare.com`
		A	2a06:98c1:50::ac40:2248^{🇺🇸 Cloudflare2a06:98c1:50::/45}
			PTR	`zariyah.ns.cloudflare.com`
		A	108.162.194.72^{🇺🇸 Cloudflare108.162.194.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zariyah.ns.cloudflare.com`
		A	162.159.38.72^{Cloudflare162.159.32.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zariyah.ns.cloudflare.com`
		A	172.64.34.72^{🇺🇸 Cloudflare172.64.34.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
			PTR	`zariyah.ns.cloudflare.com`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c09::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`bh-in-f26.1e100.net`
		A	64.233.180.27^{🇺🇸 Google64.233.180.0/24}
			PTR	`on-in-f27.1e100.net`
			PTR	`pe-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c0f::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	108.177.123.27^{🇺🇸 Google108.177.123.0/24}
			PTR	`lcscld-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1b^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f27.1e100.net`
		A	172.253.116.27^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-in-f27.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1a^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f26.1e100.net`
		A	192.178.223.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f27.1e100.net`
		A	172.253.157.26^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f26.1e100.net`
TXT	`v=spf1 include:_spf.google.com ~all`
HTTPS	HTTP/3, HTTP/2 ✓ hints match
		IPv4 hints	104.21.37.118, 172.67.207.215
		IPv6 hints	2606:4700:3031::6815:2576, 2606:4700:3037::ac43:cfd7
		ECH	X25519, HKDF-SHA256 + AES-128-GCM draft, id=193, name=cloudflare-ech.com
SOA	`rick.ns.cloudflare.com`dns@cloudflare.com serial=2408088006

`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=1783735152

Previously MX for

fwave.com

Same first word

fwave.co.jp

fwave.com

Similar names

wefav.com

afewv.com

wavef.com

DNS History

17 records (11 active, 6 former)

○NSdns.site5.com2015-06-01 → 2017-04-19 · 4 obs

● 2015-06-01 19:04:00
● 2017-04-19 03:42:20
○ 2026-02-24 19:17:52
○ 2026-07-11 02:21:14

○NSdns2.site5.com2015-06-01 → 2017-04-19 · 4 obs

● 2015-06-01 19:04:00
● 2017-04-19 03:42:20
○ 2026-02-24 19:17:52
○ 2026-07-11 02:21:14

●NSrick.ns.cloudflare.com2026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

●NSzariyah.ns.cloudflare.com2026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

●MXalt1.aspmx.l.google.com2026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

●MXalt2.aspmx.l.google.com2026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

●MXalt3.aspmx.l.google.com2026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

●MXalt4.aspmx.l.google.com2026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

●MXaspmx.l.google.com2026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

○MXfwave.com2015-06-01 → 2017-04-19 · 4 obs

● 2015-06-01 19:04:00
● 2017-04-19 03:42:20
○ 2026-02-24 19:17:52
○ 2026-07-11 02:21:14

●A104.21.37.1182026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

○A129.121.2.2162016-09-24 → 2017-04-19 · 5 obs

○ 2016-04-12 07:52:22
● 2016-09-24 17:45:52
● 2017-04-19 03:42:20
○ 2026-02-24 19:17:52
○ 2026-07-11 02:21:14

●A172.67.207.2152026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

○A174.120.252.822015-06-01 → 2016-04-12 · 4 obs

● 2015-06-01 19:04:00
● 2016-04-12 07:52:22
○ 2016-09-24 17:45:52
○ 2026-07-11 02:21:14

○A2606:4700:3030::ac43:cfd72026-02-24 → 2026-06-11 · 5 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-06-11 18:56:24
○ 2026-06-30 15:34:42
○ 2026-07-11 02:21:14

●A2606:4700:3031::6815:25762026-02-24 → 2026-07-11 · 3 obs

○ 2017-04-19 03:42:20
● 2026-02-24 19:17:52
● 2026-07-11 02:21:14

●A2606:4700:3037::ac43:cfd72026-06-30 → 2026-07-11 · 3 obs

○ 2026-06-11 18:56:24
● 2026-06-30 15:34:42
● 2026-07-11 02:21:14

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
com	a.gtld-servers.net, b.gtld-servers.net, c.gtld-servers.net, d.gtld-servers.net...	-
fwave.com	rick.ns.cloudflare.com, zariyah.ns.cloudflare.com	12 records

✅ Authoritative Response

Server:108.162.194.72

NS records: rick.ns.cloudflare.com, zariyah.ns.cloudflare.com

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for fwave.com (unsigned zone)

⏱️ Timing

Total: 131ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`172.67.207.215, 104.21.37.118`
AAAA	2	`2606:4700:3031::6815:2576, 2606:4700:3037::ac43:cfd7`
NS	2	`rick.ns.cloudflare.com, zariyah.ns.cloudflare.com`
MX	5	`aspmx.l.google.com (pri: 1), alt3.aspmx.l.google.com (pri: 10)...`
TXT	1	`v=spf1 include:_spf.google.com ~all`
HTTPS	1	`{"priority":1,"target":".","alpn":["h3",`
SOA	1	`rick.ns.cloudflare.com dns.cloudflare.co`

📌 Glue Records Collected

Total: 12

Out-of-bailiwick: 12 (rick.ns.cloudflare.com, rick.ns.cloudflare.com, rick.ns.cloudflare.com...)

Analysis

IP Addresses

fwave.com resolves to four IP addresses: 104.21.37.118, 172.67.207.215, 2606:4700:3031::6815:2576 and 2606:4700:3037::ac43:cfd7.

tarragonastore.com, ns2.essaymastershub.com, vcrhb.com and two other host names share IP numbers with fwave.com.

Name Servers

fwave.com uses two name servers for its delegation: rick.ns.cloudflare.com and zariyah.ns.cloudflare.com.

fwave.com uses the same name servers as several other domains — among them gala-betgiris.vip, alnisir.net, roweryostrowiec.pl and two more.

fwave.com has at least partial name server overlap with other domains, such as cypo.eu, botcorp.io, buceta.info and two others.

It is common to see these name servers used together with name servers andy.ns.cloudflare.com and ingrid.ns.cloudflare.com.

Hostnames that resolve to 6 IP addresses:

Hostname rick.ns.cloudflare.com directs to 108.162.193.139, 172.64.33.139 and 173.245.59.139 along with 3 other IP addresses.

Hostname zariyah.ns.cloudflare.com directs to 108.162.194.72, 162.159.38.72 and 172.64.34.72 along with 3 other IP addresses.

Mail Servers

fwave.com is handled by five mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com and two others.

fwave.com has at least partial mail server overlap with other domains such as withdipp.com, berken.org, cfgi.io and two more.

These mail servers commonly co-occur with mail servers alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and 3 others.

Hostnames that resolve to two IP addresses:

aspmx.l.google.com directs traffic to 64.233.180.27 and 2607:f8b0:4004:c09::1a.

alt1.aspmx.l.google.com directs traffic to 108.177.123.27 and 2800:3f0:4003:c0f::1a.

alt2.aspmx.l.google.com directs traffic to 172.253.116.27 and 2a00:1450:400b:c02::1b.

alt3.aspmx.l.google.com directs traffic to 192.178.223.26 and 2a00:1450:4009:c0f::1a.

alt4.aspmx.l.google.com directs traffic to 172.253.157.26 and 2a00:1450:400c:c23::1b.