Hostname

iam.homewithgod.com

Last fetched Sun, 06 Sep 2026 20:16:24 GMT

iam.homewithgod.com resolves to 139.162.174.209, announced in 139.162.160.0/19 by AKAMAI-LINODE-AP - Akamai Connected Cloud in DE. iam.homewithgod.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

Resolution chain

139.162.174.209
139.162.160.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
139.162.181.76
139.162.160.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
172.104.149.86
172.104.128.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
172.104.203.186
172.104.202.0/23 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
172.104.251.198
172.104.224.0/19 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Frankfurt am Main, DE
192.155.84.236
192.155.80.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
23.239.3.104
23.239.0.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
23.239.4.93
23.239.0.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
66.175.216.36
66.175.216.0/21 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US
74.207.241.245
74.207.240.0/20 · AKAMAI-LINODE-AP - Akamai Connected Cloud · Fremont, US

Attribution

akamai

ORIGIN_AS

Subdomains

Subdomain
mail.iam.homewithgod.com
www.iam.homewithgod.com

Showing 2 of 2 subdomains (2 per page).

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

Mail and authentication

Nameservers

damao.ns.giantpanda.com
yangguang.ns.giantpanda.com

MX records

mail.mailerhost.net

SPF policy

ip: fd43:c0d1:c090::/48

Threat-feed evidence

History

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