megaforce.be - dns.ninja

`megaforce.be`

DNSSEC	⚠️ Not signed
A	52.232.20.14^{🇳🇱 Microsoft52.224.0.0/11 MICROSOFT}
NS	`ns1.openprovider.nl` ⭐
		A	2400:cb00:2049:1::a29f:1a0a^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.26.10^{Cloudflare162.159.26.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns2.openprovider.be`
		A	2400:cb00:2049:1::a29f:1b60^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.27.96^{Cloudflare162.159.27.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
NS	`ns3.openprovider.eu`
		A	2400:cb00:2049:1::a29f:3059^{🇺🇸 Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street}
		A	162.159.48.89^{Cloudflare162.159.48.0/20 , Inc. 101 Townsend Street, San Francisco, California 94107, US}
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f27.1e100.net`
		A	172.253.122.26^{🇺🇸 Google172.253.122.0/24}
			PTR	`bh-in-f26.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:2801::1b^{🇺🇸 Google2607:f8b0::/32}
			PTR	`lcausi-in-f27.1e100.net`
		A	192.178.128.27^{🇺🇸 Google192.178.128.0/24}
			PTR	`lcausi-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2607:f8b0:4023:3003::1a^{🇺🇸 Google2607:f8b0::/32}
			PTR	`yulnkjt-in-f26.1e100.net`
		A	172.253.145.26^{🇺🇸 Google172.253.145.0/24}
			PTR	`yulnkjt-in-f26.1e100.net`
MX	`alt3.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:4009:c0f::1b^{🇬🇧 Google2a00:1450:4009::/48}
			PTR	`yulhrs-in-f27.1e100.net`
		A	192.178.223.27^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f27.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c00::1b^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`ws-in-f27.1e100.net`
			PTR	`ws-in-x1b.1e100.net`
		A	173.194.76.27^{🇺🇸 Google173.194.76.0/24}
			PTR	`ws-in-f27.1e100.net`
SOA	`ns1.openprovider.nl`dns@openprovider.eu 2020-04-27 #1

`be`

	DNSSEC	🔒 Signed (DS record present)
	NS	`a.nsset.be` ⭐
	NS	`b.nsset.be`
	NS	`c.nsset.be`
	NS	`d.nsset.be`
	NS	`y.nsset.be`
	NS	`z.nsset.be`
	SOA	`a.nsset.be`be-hostmaster@dnsbelgium.be serial=1028248163

Subdomains

mail.megaforce.be

www.megaforce.be

Same first word

megaforce.be

megaforce.at

megaforce.org

megaforce.mx

megaforce.ca

megaforce.de

megaforce.com

megaforce.net.ua

megaforce.co.il

megaforce.fr

megaforce.nl

megaforce.net

megaforce.eu

megaforce.com.tw

megaforce.co.za

megaforce.dyndns.org

megaforce.com.ua

megaforce.audio

Similar names

DNS History

14 records (9 active, 5 former)

○NSns1.ns-1.be2015-08-09 → 2017-03-28 · 4 obs

● 2015-08-09 22:27:02
● 2017-03-28 11:19:54
○ 2026-03-04 09:39:20
○ 2026-06-04 14:01:24

●NSns1.openprovider.nl2026-03-04 → 2026-06-04 · 3 obs

○ 2017-03-28 11:19:54
● 2026-03-04 09:39:20
● 2026-06-04 14:01:24

○NSns2.ns-1.be2015-08-09 → 2017-03-28 · 4 obs

● 2015-08-09 22:27:02
● 2017-03-28 11:19:54
○ 2026-03-04 09:39:20
○ 2026-06-04 14:01:24

●NSns2.openprovider.be2026-03-04 → 2026-06-04 · 3 obs

○ 2017-03-28 11:19:54
● 2026-03-04 09:39:20
● 2026-06-04 14:01:24

○NSns3.ns-1.be2015-08-09 → 2017-03-28 · 4 obs

● 2015-08-09 22:27:02
● 2017-03-28 11:19:54
○ 2026-03-04 09:39:20
○ 2026-06-04 14:01:24

●NSns3.openprovider.eu2026-03-04 → 2026-06-04 · 3 obs

○ 2017-03-28 11:19:54
● 2026-03-04 09:39:20
● 2026-06-04 14:01:24

●MXalt1.aspmx.l.google.com2015-08-09 → 2026-06-04 · 2 obs

● 2015-08-09 22:27:02
● 2026-06-04 14:01:24

●MXalt2.aspmx.l.google.com2015-08-09 → 2026-06-04 · 2 obs

● 2015-08-09 22:27:02
● 2026-06-04 14:01:24

●MXalt3.aspmx.l.google.com2015-08-09 → 2026-06-04 · 2 obs

● 2015-08-09 22:27:02
● 2026-06-04 14:01:24

●MXalt4.aspmx.l.google.com2015-08-09 → 2026-06-04 · 2 obs

● 2015-08-09 22:27:02
● 2026-06-04 14:01:24

●MXaspmx.l.google.com2015-08-09 → 2026-06-04 · 2 obs

● 2015-08-09 22:27:02
● 2026-06-04 14:01:24

●A52.232.20.142026-03-04 → 2026-06-04 · 3 obs

○ 2017-03-28 11:19:54
● 2026-03-04 09:39:20
● 2026-06-04 14:01:24

○A88.151.241.232015-08-09 → 2015-12-27 · 4 obs

● 2015-08-09 22:27:02
● 2015-12-27 18:56:14
○ 2016-09-12 04:40:52
○ 2026-06-04 14:01:24

○A88.151.245.752016-09-12 → 2017-03-28 · 5 obs

○ 2015-12-27 18:56:14
● 2016-09-12 04:40:52
● 2017-03-28 11:19:54
○ 2026-03-04 09:39:20
○ 2026-06-04 14:01:24

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
be	d.nsset.be, b.nsset.be, z.nsset.be, c.nsset.be...	-
megaforce.be	ns3.openprovider.eu, ns2.openprovider.be, ns1.openprovider.nl	-

✅ Authoritative Response

Server:162.159.27.96

NS records: ns3.openprovider.eu, ns2.openprovider.be, ns1.openprovider.nl

🔒 DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for megaforce.be (unsigned zone)

⏱️ Timing

Total: 1347ms | Queries: -

📄 Records

Type	Count	Sample Data
A	1	`52.232.20.14`
NS	3	`ns1.openprovider.nl, ns2.openprovider.be...`
MX	5	`ALT3.ASPMX.L.GOOGLE.COM (pri: 10), ALT4.ASPMX.L.GOOGLE.COM (pri: 10)...`
SOA	1	`ns1.openprovider.nl dns.openprovider.eu`

Analysis

Hierarchy

The parent domain of mail.megaforce.be and www.megaforce.be is megaforce.be.

IP Addresses

megaforce.be directs to one IP number, which is 52.232.20.14.

Among the host names that share IP numbers with megaforce.be are rosscom.biz, compudealsweb.be, comparts.be and two others.

Name Servers

megaforce.be has three name servers — ns2.openprovider.be, ns3.openprovider.eu and ns1.openprovider.nl.

megaforce.be partially shares its NS delegation with several other domains, including minigolfboskoop.nl, fr-pickup-choix.com, whets.net and two others.

Each of ns2.openprovider.be, ns3.openprovider.eu and ns1.openprovider.nl points to two IP numbers. ns2.openprovider.be points to 162.159.27.96 and 2400:cb00:2049:1::a29f:1b60. ns3.openprovider.eu points to 162.159.48.89 and 2400:cb00:2049:1::a29f:3059. ns1.openprovider.nl points to 162.159.26.10 and 2400:cb00:2049:1::a29f:1a0a.

Mail Servers

megaforce.be uses 5 mail servers: aspmx.l.google.com, alt1.aspmx.l.google.com, alt2.aspmx.l.google.com plus two additional ones.

megaforce.be shares at least some of its mail servers with other domains — for example ns500698.ns500758.ns500759.ns500759.ns500758.ns500735.ns500735.ns500735.ns500698.ns500708.ns500708.ns500619.ns500652.ns500576.trackreceptor.com, ns500759.ns500759.ns500759.ns500758.ns500735.ns500698.ns500735.ns500698.ns500698.ns500698.ns500698.ns500698.ns500708.ns500576.ns500576.ns500619.ns500576.trackreceptor.com, ns500734.ns500699.ns500699.ns500693.ns500693.ns500734.ns500693.ns500683.ns500588.ns500693.ns500699.ns500612.ns500110.dtrkdll.com and two more.

These mail servers tend to co-occur with alt3.aspmx.l.google.com, alt4.aspmx.l.google.com, aspmx2.googlemail.com and three additional mail servers.

Hosts with two IP numbers each:

aspmx.l.google.com resolves to 172.253.122.26 and 2607:f8b0:4004:c25::1b.

alt1.aspmx.l.google.com resolves to 192.178.128.27 and 2607:f8b0:4023:2801::1b.

alt2.aspmx.l.google.com resolves to 172.253.145.26 and 2607:f8b0:4023:3003::1a.

alt3.aspmx.l.google.com resolves to 192.178.223.27 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com resolves to 173.194.76.27 and 2a00:1450:400c:c00::1b.