ref.fm - dns.ninja

ref.fm

DNSSEC⚠️ Not signed
A103.168.172.37πŸ‡ΊπŸ‡Έ FASTMAILPTYLTD-AS-AP103.168.172.0/24 Fastmail Pty Ltd Level 2, 114 William Street
PTRwww.messagingengine.com
A103.168.172.52πŸ‡ΊπŸ‡Έ FASTMAILPTYLTD-AS-AP103.168.172.0/24 Fastmail Pty Ltd Level 2, 114 William Street
NSfmns1.messagingengine.com ⭐ ⚠️ Not in parent delegation
A162.159.24.253Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRfmns1.messagingengine.com
NSfmns2.messagingengine.com ⚠️ Not in parent delegation
A162.159.25.114Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRfmns2.messagingengine.com
NSns1.messagingengine.com ⚠️ Not in zone NS records
A162.159.24.178Cloudflare162.159.24.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns1.messagingengine.com
NSns2.messagingengine.com ⚠️ Not in zone NS records
A162.159.25.191Cloudflare162.159.25.0/24 , Inc. 101 Townsend Street, San Francisco, California 94107, US
PTRns2.messagingengine.com
SOAfmns1.messagingengine.compostmaster@messagingengine.com 2026-06-01 #0

fm

DNSSECπŸ”’ Signed (DS record present)
NSns0.centralnic.net ⭐
NSa.nic.fm
NSb.nic.fm
NSc.nic.fm
NSd.nic.fm
NSe.nic.fm
NSf.nic.fm
SOAns0.centralnic.netitmanager@fsmtc.fm serial=309691

Same first word

Similar names

DNS History

6 records (6 active, 0 former)

NSfmns1.messagingengine.comfmns2.messagingengine.comns1.messagingengine.comns2.messagingengine.comA103.168.172.37103.168.172.52
●NSfmns1.messagingengine.com2026-05-01 β†’ 2026-06-04 Β· 2 obs
● 2026-05-01 10:19:24
● 2026-06-04 01:45:22
●NSfmns2.messagingengine.com2026-05-01 β†’ 2026-06-04 Β· 2 obs
● 2026-05-01 10:19:24
● 2026-06-04 01:45:22
●NSns1.messagingengine.com2026-05-01 β†’ 2026-06-04 Β· 2 obs
● 2026-05-01 10:19:24
● 2026-06-04 01:45:22
●NSns2.messagingengine.com2026-05-01 β†’ 2026-06-04 Β· 2 obs
● 2026-05-01 10:19:24
● 2026-06-04 01:45:22
●A103.168.172.372026-05-01 β†’ 2026-06-04 Β· 2 obs
● 2026-05-01 10:19:24
● 2026-06-04 01:45:22
●A103.168.172.522026-05-01 β†’ 2026-06-04 Β· 2 obs
● 2026-05-01 10:19:24
● 2026-06-04 01:45:22

πŸ” DNS Trace

πŸ“‹ Delegation Chain

ZoneNameserversGlue
fmd.nic.fm, b.nic.fm, a.nic.fm, c.nic.fm...-
ref.fmns1.messagingengine.com, ns2.messagingengine.com-

βœ… Authoritative Response

Server:162.159.24.178

NS records: ns1.messagingengine.com, ns2.messagingengine.com

πŸ”’ DNSSEC Status

⚠️ Insecure (no DNSSEC)

No DS record for ref.fm (unsigned zone)

⏱️ Timing

Total: 325ms | Queries: -

πŸ“„ Records

TypeCountSample Data
A2103.168.172.37, 103.168.172.52
NS2fmns1.messagingengine.com, fmns2.messagingengine.com
SOA1fmns1.messagingengine.com postmaster.mes

Analysis

IP Addresses

ref.fm points to two IP numbers: 103.168.172.37 and 103.168.172.52.

chrishamilton.org, braingames.careers, lmfeja.com and two other host names share IP numbers with ref.fm.

Name Servers

Authority for ref.fm is delegated across 4 name servers: fmns1.messagingengine.com, fmns2.messagingengine.com, ns1.messagingengine.com and ns2.messagingengine.com.

ref.fm has at least partial name server overlap with other domains, such as 214bankruptcy.com, mailsimon.com, jameshowat.net and two others.

It is common to see these name servers used together with name servers ns1.bouncycastlenetwork.co.uk and ns2.bouncycastlenetwork.co.uk.

Each of the four hosts fmns1.messagingengine.com, fmns2.messagingengine.com, ns1.messagingengine.com and ns2.messagingengine.com points to a single IP address β€” fmns1.messagingengine.com points to 162.159.24.253, fmns2.messagingengine.com points to 162.159.25.114, ns1.messagingengine.com points to 162.159.24.178 and ns2.messagingengine.com points to 162.159.25.191.