Skip to content

Hostname

mechanicalpower.net

Last fetched

mechanicalpower.net resolves to 104.21.44.117, announced in 104.21.32.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. mechanicalpower.net 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 · mechanicalpower.netRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/mechanicalpower.net

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
inc. mechanical power
Contact emails
ebailey@cmitsolutions.com, mechanical.power135@gmail.com, mpiadmin@mechanicalpower.net

Subdomains

Web-graph footprint

Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.

Mail and authentication

Nameservers

  • earl.ns.cloudflare.com
  • zoe.ns.cloudflare.com
  • 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

  • d332183a.ess.barracudanetworks.com
  • d332183b.ess.barracudanetworks.com

SPF policy

  • ip: 50.240.189.177/29
  • include: amazonses.com
  • include: _spf.google.com
  • include: spf.protection.outlook.com
  • include: qlmsourcing.com
  • include: _spf.mailgun.org

Threat-feed evidence

History

Related pages

Pivot from mechanicalpower.net 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: "mechanicalpower.net"})-[: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.