Skip to content

Hostname

inflcr.com

Last fetched

inflcr.com resolves to 108.156.60.24, announced in 108.156.60.0/22 by AMAZON-02 - Amazon.com, Inc. in IE. inflcr.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 · inflcr.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/inflcr.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of inflcr.com owner
Contact emails
jim@inflcr.com, jim@glowout.io, 9f92d871-dd55-473e-b867-7b72808aecc0@identity-protect.org, af9708ad-f53f-48e3-8ac3-735433c83862@identity-protect.org, ca14a0e0-de07-437b-b89d-1dd351746951@identity-protect.org

Subdomains

Subdomain
api.inflcr.com
beyondball.inflcr.com
cdn-dev.inflcr.com
cdn.inflcr.com
dash.inflcr.com
dev.inflcr.com
git.inflcr.com
help.inflcr.com
learn.inflcr.com
marketing.inflcr.com
pages.inflcr.com
production.inflcr.com

Showing 12 of 17. 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

  • ns-93.awsdns-11.com
  • ns-952.awsdns-55.net
  • ns-1484.awsdns-57.org
  • ns-1944.awsdns-51.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.googlemail.com
  • aspmx3.googlemail.com
  • mxa.mailgun.org
  • mxb.mailgun.org

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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