Skip to content

Hostname

lifeasmama.com

Last fetched

lifeasmama.com resolves to 104.21.56.19, announced in 104.21.48.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. lifeasmama.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 · lifeasmama.comRouting diversity2.4/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.5/10canon.whisper.security/host/lifeasmama.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:146
Registrant organisation
domains by proxy,
Contact emails
lifeasmama.com@domainsbyproxy.com, justin@homelifemedia.com, justin@palmerwebmarketing.com

Subdomains

Subdomain
autodiscover.lifeasmama.com
mail.lifeasmama.com
www.lifeasmama.com

Showing 3 of 3 subdomains (3 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

  • raquel.ns.cloudflare.com
  • vin.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
  • ns1.wpx.net
  • ns2.wpx.net
  • ns3.wpx.net

MX records

  • smtp.google.com
  • mail.lifeasmama.com

SPF policy

  • a: lifeasmama.com
  • mx: lifeasmama.com
  • ip: 198.60.193.34
  • ip: 198.60.193.82
  • ip: 50.31.66.204
  • ip: 67.202.92.34

Threat-feed evidence

History

Related pages

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