secure-messaging.com - dns.ninja

secure-messaging.com

DNSSEC⚠️ Not signed
A13.92.226.210πŸ‡ΊπŸ‡Έ Microsoft13.64.0.0/11 MICROSOFT
NSmdns1.appriver.com ⭐
A2400:cb00:2049:1::a29f:18c6πŸ‡ΊπŸ‡Έ Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.24.198Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
NSmdns2.appriver.com
A2400:cb00:2049:1::a29f:1964πŸ‡ΊπŸ‡Έ Cloudflare2400:cb00:2049::/48 , Inc. 101 Townsend Street
A162.159.25.100Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
MXemail2.com.1.0001.arsmtp.com ⭐
A8.31.233.248πŸ‡ΊπŸ‡Έ APPRI-18.31.233.0/24 AppRiver, LLC 1101 Gulf Breeze Parkway Gulf Breeze, FL 32561 US
PTRserver2026.appriver.com
MXemail2.com.2.0001.arsmtp.com(20)
A8.19.118.229πŸ‡ΊπŸ‡Έ AS133808.19.118.0/24 AppRiver, LLC 1101 Gulf Breeze Parkway Gulf Breeze, FL 32561 US
PTRserver2027.appriver.com
TXT_globalsign-domain-verification=iFrbibJht50yPf36Nj1gdtAJq19p9lai_u9NLAe9Xt
TXTv=spf1 include:appriver.com include:sendgrid.net include:spf.mtasv.net ~all
SOAmdns1.appriver.comdns@jomax.net 2026-03-10 #1

com

πŸ“ˆ Tranco rank: #362,674

Subdomains

Same first word

DNS History

21 records (5 active, 16 former)

20162017201820192020202120222023202420252026NSmdns1.appriver.commdns2.appriver.comns1-09.azure-dns.comns1.p01.dynect.netns15.domaincontrol.comns16.domaincontrol.comns2-09.azure-dns.netns2.p01.dynect.netns3-09.azure-dns.orgns3.p01.dynect.netns4-09.azure-dns.infons4.p01.dynect.netMXemail2.com.1.0001.arsmtp.comemail2.com.2.0001.arsmtp.comalt1.aspmx.l.google.comalt2.aspmx.l.google.comaspmx.l.google.comaspmx2.googlemail.comaspmx3.googlemail.comA13.92.226.210137.135.105.52
●NSmdns1.appriver.com2026-03-02 β†’ 2026-08-06 Β· 3 obs
β—‹ 2018-04-11 09:05:26
● 2026-03-02 10:36:10
● 2026-08-06 23:40:24
●NSmdns2.appriver.com2026-03-02 β†’ 2026-08-06 Β· 3 obs
β—‹ 2018-04-11 09:05:26
● 2026-03-02 10:36:10
● 2026-08-06 23:40:24
β—‹NSns1-09.azure-dns.com2017-12-20 β†’ 2018-04-11 Β· 5 obs
β—‹ 2017-02-18 23:18:02
● 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹NSns1.p01.dynect.net2017-02-18 β†’ 2018-04-11 Β· 6 obs
β—‹ 2016-06-23 06:30:24
● 2017-02-18 23:18:02
β—‹ 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹NSns15.domaincontrol.com2015-08-15 β†’ 2016-06-23 Β· 4 obs
● 2015-08-15 10:32:54
● 2016-06-23 06:30:24
β—‹ 2017-02-18 23:18:02
β—‹ 2026-08-06 23:40:24
β—‹NSns16.domaincontrol.com2015-08-15 β†’ 2016-06-23 Β· 4 obs
● 2015-08-15 10:32:54
● 2016-06-23 06:30:24
β—‹ 2017-02-18 23:18:02
β—‹ 2026-08-06 23:40:24
β—‹NSns2-09.azure-dns.net2017-12-20 β†’ 2018-04-11 Β· 5 obs
β—‹ 2017-02-18 23:18:02
● 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹NSns2.p01.dynect.net2017-02-18 β†’ 2017-02-18 Β· 4 obs
β—‹ 2016-06-23 06:30:24
● 2017-02-18 23:18:02
β—‹ 2017-12-20 17:27:38
β—‹ 2026-08-06 23:40:24
β—‹NSns3-09.azure-dns.org2017-12-20 β†’ 2018-04-11 Β· 5 obs
β—‹ 2017-02-18 23:18:02
● 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹NSns3.p01.dynect.net2017-02-18 β†’ 2017-02-18 Β· 4 obs
β—‹ 2016-06-23 06:30:24
● 2017-02-18 23:18:02
β—‹ 2017-12-20 17:27:38
β—‹ 2026-08-06 23:40:24
β—‹NSns4-09.azure-dns.info2017-12-20 β†’ 2018-04-11 Β· 5 obs
β—‹ 2017-02-18 23:18:02
● 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹NSns4.p01.dynect.net2017-02-18 β†’ 2017-02-18 Β· 4 obs
β—‹ 2016-06-23 06:30:24
● 2017-02-18 23:18:02
β—‹ 2017-12-20 17:27:38
β—‹ 2026-08-06 23:40:24
β—‹MXalt1.aspmx.l.google.com2015-08-15 β†’ 2018-04-11 Β· 6 obs
● 2015-08-15 10:32:54
● 2017-02-18 23:18:02
β—‹ 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹MXalt2.aspmx.l.google.com2015-08-15 β†’ 2018-04-11 Β· 6 obs
● 2015-08-15 10:32:54
● 2017-02-18 23:18:02
β—‹ 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹MXaspmx.l.google.com2015-08-15 β†’ 2018-04-11 Β· 6 obs
● 2015-08-15 10:32:54
● 2017-02-18 23:18:02
β—‹ 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹MXaspmx2.googlemail.com2015-08-15 β†’ 2018-04-11 Β· 6 obs
● 2015-08-15 10:32:54
● 2017-02-18 23:18:02
β—‹ 2017-12-20 17:27:38
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
β—‹MXaspmx3.googlemail.com2015-08-15 β†’ 2018-04-11 Β· 4 obs
● 2015-08-15 10:32:54
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24
●MXemail2.com.1.0001.arsmtp.com2026-03-02 β†’ 2026-08-06 Β· 3 obs
β—‹ 2018-04-11 09:05:26
● 2026-03-02 10:36:10
● 2026-08-06 23:40:24
●MXemail2.com.2.0001.arsmtp.com2026-03-02 β†’ 2026-08-06 Β· 3 obs
β—‹ 2018-04-11 09:05:26
● 2026-03-02 10:36:10
● 2026-08-06 23:40:24
●A13.92.226.2102026-03-02 β†’ 2026-08-06 Β· 3 obs
β—‹ 2018-04-11 09:05:26
● 2026-03-02 10:36:10
● 2026-08-06 23:40:24
β—‹A137.135.105.522015-08-15 β†’ 2018-04-11 Β· 4 obs
● 2015-08-15 10:32:54
● 2018-04-11 09:05:26
β—‹ 2026-03-02 10:36:10
β—‹ 2026-08-06 23:40:24

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
come.gtld-servers.net, i.gtld-servers.net, g.gtld-servers.net, a.gtld-servers.net...-
secure-messaging.commdns1.appriver.com, mdns2.appriver.com4 records

βœ… Authoritative Response

Server:162.159.24.198

NS records: mdns1.appriver.com, mdns2.appriver.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for secure-messaging.com (unsigned zone)

⏱️ Timing

Total: 210ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A113.92.226.210
NS2mdns1.appriver.com, mdns2.appriver.com
MX2email2.com.2.0001.arsmtp.com (pri: 20), email2.com.1.0001.arsmtp.com (pri: 10)
TXT2_globalsign-domain-verification=iFrbibJh, v=spf1 include:appriver.com include:send
SOA1mdns1.appriver.com dns.jomax.net

πŸ“Œ Glue Records Collected

Total: 4

Out-of-bailiwick: 4 (mdns1.appriver.com, mdns1.appriver.com, mdns2.appriver.com...)

Analysis

Hierarchy

secure-messaging.com is the parent domain of cdn.secure-messaging.com, help.secure-messaging.com, us1.secure-messaging.com, resources.secure-messaging.com, uk.secure-messaging.com and a few other host names.

IP Addresses

secure-messaging.com resolves to just one IP address, 13.92.226.210.

secure.email2.com is an example of another host name that shares IP numbers with secure-messaging.com.

Name Servers

secure-messaging.com has two authoritative name servers β€” mdns1.appriver.com and mdns2.appriver.com.

secure-messaging.com shares its NS records with other domains, for example zixappriver.com, smtpip.com, arsmtp.com and two others.

The name servers for secure-messaging.com overlap at least partially with those of other domains β€” for example email2.com.

These name servers are frequently seen alongside the name servers masterdns.appriver.corp.

Both mdns1.appriver.com and mdns2.appriver.com have two IP addresses each. mdns1.appriver.com resolves to 162.159.24.198 and 2400:cb00:2049:1::a29f:18c6; mdns2.appriver.com resolves to 162.159.25.100 and 2400:cb00:2049:1::a29f:1964.

Mail Servers

secure-messaging.com is served by two mail servers, email2.com.1.0001.arsmtp.com and email2.com.2.0001.arsmtp.com.

secure-messaging.com shares its mail server configuration with other domains, such as secure-notification.com and email2.com.

email2.com.1.0001.arsmtp.com and email2.com.2.0001.arsmtp.com each resolve to one IP number: email2.com.1.0001.arsmtp.com points to 8.31.233.248 and email2.com.2.0001.arsmtp.com points to 8.19.118.229.