securem.be - dns.ninja

🛡️Domain Reputation CheckBlocklist, phishing & malware status→

`securem.be`

DNSSEC	🔒 Signed (DS record present)
A	199.60.103.70^{🇺🇸 CLOUDFLARESPECTRUM199.60.103.0/24 MNT-HUBSP-8 route 199.060.103.000/24 AS209242}
A	199.60.103.170^{🇺🇸 CLOUDFLARESPECTRUM199.60.103.0/24 MNT-HUBSP-8 route 199.060.103.000/24 AS209242}
NS	`dns107.ovh.net` ⭐
		A	2001:41d0:d01:100::2^{🇫🇷 OVH2001:41d0::/32 IPv6}
			PTR	`dns107.ovh.net`
		A	5.196.41.137^{🇫🇷 OVH5.196.0.0/16}
			PTR	`dns107.ovh.net`
NS	`ns107.ovh.net`
		A	2001:41d0:b00:fb00::2^{🇫🇷 OVH2001:41d0::/32 IPv6}
			PTR	`ns107.ovh.net`
		A	5.135.65.209^{🇫🇷 OVH5.135.0.0/16}
			PTR	`ns107.ovh.net`
MX	`aspmx.l.google.com` ⭐
		A	2607:f8b0:4004:c25::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadtq-in-f27.1e100.net`
		A	172.253.63.27^{🇺🇸 Google172.253.63.0/24}
			PTR	`bi-in-f27.1e100.net`
MX	`smtp.google.com` ⭐
		A	2607:f8b0:4004:c1b::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f26.1e100.net`
		A	2607:f8b0:4004:c1b::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`wv-in-f27.1e100.net`
		A	2607:f8b0:4004:c29::1a^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f26.1e100.net`
		A	2607:f8b0:4004:c29::1b^{🇺🇸 Google2607:f8b0:4004::/48}
			PTR	`yuiadum-in-f27.1e100.net`
		A	142.251.163.26^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f26.1e100.net`
		A	142.251.163.27^{🇺🇸 Google142.251.163.0/24}
			PTR	`wv-in-f27.1e100.net`
		A	142.251.167.26^{🇺🇸 Google142.251.167.0/24}
			PTR	`ww-in-f26.1e100.net`
		A	173.194.45.26^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f26.1e100.net`
		A	173.194.45.27^{🇺🇸 Google173.194.0.0/16}
			PTR	`yuiadum-in-f27.1e100.net`
MX	`alt1.aspmx.l.google.com`⁽⁵⁾
		A	2800:3f0:4003:c14::1a^{🇨🇱 Google2800:3f0:4003::/48}
		A	192.178.234.27^{🇺🇸 Google192.178.0.0/15}
			PTR	`ncsclj-in-f27.1e100.net`
MX	`alt2.aspmx.l.google.com`⁽⁵⁾
		A	2a00:1450:400b:c02::1a^{🇮🇪 Google2a00:1450:400b::/48}
			PTR	`dj-in-f26.1e100.net`
		A	172.253.116.26^{🇺🇸 Google172.253.116.0/24}
			PTR	`dj-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.26^{🇺🇸 Google192.178.223.0/24}
			PTR	`yulhrs-in-f26.1e100.net`
MX	`alt4.aspmx.l.google.com`⁽¹⁰⁾
		A	2a00:1450:400c:c23::1a^{🇧🇪 Google2a00:1450:400c::/48}
			PTR	`yubrupd-in-f26.1e100.net`
		A	172.253.157.27^{🇺🇸 Google172.253.0.0/16}
			PTR	`yubrupd-in-f27.1e100.net`
TXT	`google-site-verification=xZ4wvbRZ3_2pXt3qwWTk-9GjDwPdslteVzYQuNPGB3Y`
TXT	`google-site-verification=O1qbA4cGW_73lkGRemO9KComOEtmyDDFYLWE0cvdXys`
TXT	`v=spf1 include:_spf.google.com include:amazonses.com include:outbound.smtp.wi...`
TXT	`klaviyo-site-verification=TZQ2Pb`
TXT	`google-site-verification=oj53WXa_gwZjXlZ0EJ_82DfxuzTM2POOeKWy3Jo2aIQ`
SOA	`dns107.ovh.net`tech@ovh.net serial=2086656972

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

Same first word

securem.de

securem.be

securem.es

securem.eu.com

securem.net

securem.gov.il

securem.com.au

securem.eu

Similar names

cemesur.com

msecure.org

sumerce.ca

msecure.com.my

curseme.com

msecure.co

cemersu.com

mercues.com

sumerce.com

mercues.eu

rescume.com

ecmuser.com

mrescue.com

smecure.com

resecum.com

sumerce.nyc

muserec.com

msecure.pl

msecure.com.tr

cremeus.com

securme.com

mescure.com

secumer.com

rescuem.com

ceremus.com

msecure.jp

rescuem.org

sumerce.net

msecure.eu

msecure.ru

mercues.net

msecure.de

msecure.com

msecure.net

cremuse.com

mercues.fr

DNS History

14 records (10 active, 4 former)

○NSdns102.ovh.net2015-07-06 → 2017-07-03 · 4 obs

● 2015-07-06 02:37:34
● 2017-07-03 23:47:54
○ 2026-04-04 05:27:12
○ 2026-08-15 19:33:28

●NSdns107.ovh.net2026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

○NSns102.ovh.net2015-07-06 → 2017-07-03 · 4 obs

● 2015-07-06 02:37:34
● 2017-07-03 23:47:54
○ 2026-04-04 05:27:12
○ 2026-08-15 19:33:28

●NSns107.ovh.net2026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

●MXalt1.aspmx.l.google.com2026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

●MXalt2.aspmx.l.google.com2026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

●MXalt3.aspmx.l.google.com2026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

●MXalt4.aspmx.l.google.com2026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

●MXaspmx.l.google.com2026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

○MXsecurem-be.mail.protection.outlook.com2015-07-06 → 2017-07-03 · 4 obs

● 2015-07-06 02:37:34
● 2017-07-03 23:47:54
○ 2026-04-04 05:27:12
○ 2026-08-15 19:33:28

●MXsmtp.google.com2026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

●A199.60.103.1702026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

●A199.60.103.702026-04-04 → 2026-08-15 · 3 obs

○ 2017-07-03 23:47:54
● 2026-04-04 05:27:12
● 2026-08-15 19:33:28

○A213.186.33.872015-07-06 → 2017-07-03 · 4 obs

● 2015-07-06 02:37:34
● 2017-07-03 23:47:54
○ 2026-04-04 05:27:12
○ 2026-08-15 19:33:28

🔍 DNS Trace

📋 Delegation Chain

Zone	Nameservers	Glue
be	a.nsset.be, b.nsset.be, c.nsset.be, d.nsset.be...	12 records
securem.be	ns107.ovh.net, dns107.ovh.net	-

✅ Authoritative Response

Server:5.135.65.209

NS records: ns107.ovh.net, dns107.ovh.net

🔒 DNSSEC Status

🔐 Secure (DNSSEC validated)

Chain of trust verified from root to domain

⏱️ Timing

Total: 2570ms | Queries: -

📄 Records

Type	Count	Sample Data
A	2	`199.60.103.170, 199.60.103.70`
NS	2	`ns107.ovh.net, dns107.ovh.net`
MX	6	`alt1.aspmx.l.google.com (pri: 5), alt2.aspmx.l.google.com (pri: 5)...`
TXT	5	`google-site-verification=oj53WXa_gwZjXlZ, v=spf1 include:_spf.google.com include:a...`
SOA	1	`dns107.ovh.net tech.ovh.net`

📌 Glue Records Collected

Total: 12

In-bailiwick: 12 (a.nsset.be, a.nsset.be, b.nsset.be...)

Analysis

IP Addresses

securem.be points to the IP addresses 199.60.103.70 and 199.60.103.170

Additional host names — benefitbay.com, getguide.com, meteoor.nl and two others — share IP numbers with securem.be.

Name Servers

DNS delegation for securem.be points to two name servers: dns107.ovh.net and ns107.ovh.net.

securem.be shares its name server setup with other domains, including ucpmc.ne, bouddhaspa.com, creasticbracelet.fr and two others.

dns107.ovh.net directs to 5.196.41.137 and 2001:41d0:d01:100::2. ns107.ovh.net directs to 5.135.65.209 and 2001:41d0:b00:fb00::2. Each host name carries two IP addresses.

Mail Servers

securem.be accepts email via 6 mail servers: smtp.google.com, aspmx.l.google.com, alt1.aspmx.l.google.com and 3 other.

securem.be shares mail servers — at least in part — with other domains, including transontario.ca, lm-centers.com, ns500759.ns500698.ns500759.ns500698.ns500735.ns500698.ns500736.ns500698.ns500736.ns500698.ns500576.ns500576.trackreceptor.com and two others.

These mail servers are frequently used alongside mail servers alt2.aspmx.l.google.com, alt3.aspmx.l.google.com, alt4.aspmx.l.google.com and 4 other.

Host names with 9 IP numbers:

smtp.google.com has IP addresses 142.251.163.26, 142.251.163.27 and 142.251.167.26, plus 6 other.

Host names with two IP numbers:

aspmx.l.google.com has two IP addresses: 172.253.63.27 and 2607:f8b0:4004:c25::1b.

alt1.aspmx.l.google.com has two IP addresses: 192.178.234.27 and 2800:3f0:4003:c14::1a.

alt2.aspmx.l.google.com has two IP addresses: 172.253.116.26 and 2a00:1450:400b:c02::1a.

alt3.aspmx.l.google.com has two IP addresses: 192.178.223.26 and 2a00:1450:4009:c0f::1b.

alt4.aspmx.l.google.com has two IP addresses: 172.253.157.27 and 2a00:1450:400c:c23::1a.