Skip to content

Hostname

desertmt.com

Last fetched

desertmt.com resolves to 208.91.112.55, announced in 208.91.112.0/24 by FORTINET - Fortinet Inc. in CA. desertmt.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · desertmt.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.0/10canon.whisper.security/host/desertmt.com

Resolution chain

IPv6 resolution

No AAAA record for desertmt.com is recorded in WhisperGraph.

Attribution

fortinet

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
perfect privacy,
Contact emails
ba75m6up9jn@networksolutionsprivateregistration.com, f88dk3ww3fx@networksolutionsprivateregistration.com, ka85r7de2pr@networksolutionsprivateregistration.com, z89n388z68s@networksolutionsprivateregistration.com, zy9z48vu6v4@networksolutionsprivateregistration.com

Subdomains

Mail and authentication

Nameservers

  • ns1.desertmt.com
  • ns2.desertmt.com
  • ns3.desertmt.com

MX records

  • mx1.hc6853-45.iphmx.com
  • mx2.hc6853-45.iphmx.com

SPF policy

  • ip: 158.247.16.0/20
  • ip: 143.244.80.0/20
  • ip: 54.174.56.0/21
  • ip: 50.31.61.116/32
  • ip: 168.245.121.127/32
  • ip: 18.208.124.128/25
  • ip: 8.24.204.16/31
  • ip: 8.24.204.18/32
  • ip: 128.242.118.200/32
  • ip: 168.245.126.209/32
  • ip: 147.154.97.253/32
  • ip: 168.245.14.77/32
  • ip: 8.24.204.8/29
  • mx: desertmt.com
  • include: spf.emailsignatures365.com
  • include: _spf.intacct.com
  • exists: %{i}.spf.hc6853-45.iphmx.com
  • include: spf.protection.outlook.com
  • include: sg.sendclubmail.com
  • include: 6851990.spf10.hubspotemail.net
  • include: sendgrid.net
  • ip: 174.79.27.131
  • ip: 64.34.135.251
  • ip: 69.90.79.90

Threat-feed evidence

History

Related pages

Pivot from desertmt.com into the addresses, networks and registries it depends on.

Cypher and MCP

Reproduce this hostname's resolution chain against graph.whisper.security:

MATCH (h:HOSTNAME {name: "desertmt.com"})-[:RESOLVES_TO]->(ip:IPV4)
      -[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.