Skip to content

Hostname

jemworks.com

Last fetched

jemworks.com resolves to 199.26.87.174, announced in 199.26.84.0/22 by DFW-DATACENTER - DFW Datacenter in US. jemworks.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 · jemworks.comRouting diversity1.5/10Peering density1.2/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/jemworks.com

Resolution chain

IPv6 resolution

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

Attribution

dfw

MAIL_RECEIVER, ORIGIN_AS

WHOIS identity

Registrar
iana:48
Registrant organisation
john mac
Contact emails
info@jemworks.com

Subdomains

Subdomain
autodiscover.jemworks.com
cpanel.jemworks.com
cpcalendars.jemworks.com
cpcontacts.jemworks.com
mail.jemworks.com
old-novi-tec.jemworks.com
secure.jemworks.com
webdisk.jemworks.com
webmail.jemworks.com
whm.jemworks.com
www.jemworks.com

Showing 11 of 14. View all subdomains →

Mail and authentication

Nameservers

  • ns-us07.mithrilnetwork.com
  • ns-us08.mithrilnetwork.com
  • ns1.jem-tech.net
  • ns2.jem-tech.net
  • a.root-servers.net
  • b.root-servers.net
  • c.root-servers.net
  • d.root-servers.net
  • e.root-servers.net
  • f.root-servers.net
  • g.root-servers.net
  • h.root-servers.net
  • i.root-servers.net
  • j.root-servers.net
  • k.root-servers.net
  • l.root-servers.net
  • m.root-servers.net

MX records

  • jemworks.com

SPF policy

  • a: jemworks.com
  • mx: jemworks.com
  • a: spf.mithrilnetwork.com
  • ip: 199.26.87.140
  • ip: 199.26.87.174

Threat-feed evidence

History

Related pages

Pivot from jemworks.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: "jemworks.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.