Skip to content

Hostname

intangles.com

Last fetched

intangles.com resolves to 13.227.192.100, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. intangles.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 · intangles.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.3/10canon.whisper.security/host/intangles.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
intangles lab pvt.
Contact emails
anup@intangles.com

Subdomains

Subdomain
apis.intangles.com
b-inroute.intangles.com
b-next-inroute.intangles.com
brahma.intangles.com
deployment.intangles.com
device.intangles.com
eim.intangles.com
endpointcentral.intangles.com
eu.intangles.com
events-server.intangles.com
fgt.intangles.com
https-test.intangles.com

Showing 12 of 42. View all subdomains →

Mail and authentication

Nameservers

  • ns-360.awsdns-45.com
  • ns-388.awsdns-48.com
  • ns-921.awsdns-51.net
  • ns-929.awsdns-52.net
  • ns-1105.awsdns-10.org
  • ns-1287.awsdns-32.org
  • ns-1750.awsdns-26.co.uk
  • ns-2011.awsdns-59.co.uk

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

SPF policy

  • include: _spf.google.com
  • include: spf.mandrillapp.com
  • include: sender.zohoinvoice.com
  • include: sender.zoho-books.in

Threat-feed evidence

History

Related pages

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