Skip to content

Hostname

processmap.com

Last fetched

processmap.com resolves to 130.211.202.70, announced in 130.211.192.0/20 by GOOGLE-CLOUD-PLATFORM - Google LLC in US. processmap.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 · processmap.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint5.2/10canon.whisper.security/host/processmap.com

Resolution chain

IPv6 resolution

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

Attribution

Google

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of processmap.com owner
Contact emails
dns@processmap.com, jgarimella@processmap.com, rmathieu@processmap.com, 162ef799-925a-477d-8e95-1f15ee729771@identity-protect.org, cc9ba3ec-732a-4295-88ec-be41ec44c40f@identity-protect.org

Subdomains

Subdomain
1226474-rs03.processmap.com
albemarle.processmap.com
allergan.processmap.com
alticehse.processmap.com
api.processmap.com
apps.processmap.com
atotech.processmap.com
baeus.processmap.com
barilla.processmap.com
bungeehs.processmap.com
chefs.processmap.com

Showing 11 of 88. View all subdomains →

Web-graph footprint

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

Sample inbound links

Sample outbound links

Mail and authentication

Nameservers

  • a1.uberns.com
  • b1.uberns.com
  • a1.uberns.net
  • b1.uberns.net
  • b1.uberns.org

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • ms50977373.msv1.invalid
  • processmap-com.mail.protection.outlook.com

SPF policy

  • include: _spf.processmap_com._d.easydmarc.pro

Threat-feed evidence

History

Related pages

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