Skip to content

Hostname

pentagonspace.in

Last fetched

pentagonspace.in resolves to 106.51.80.18, announced in 106.51.64.0/19 by CABLELITE-AS-AP - Atria Convergence Technologies Pvt. Ltd. Broadband Internet Service Provider INDIA in IN. pentagonspace.in 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 · pentagonspace.inRouting diversity1.5/10Peering density4.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency3.3/10Resolver footprint8.3/10canon.whisper.security/host/pentagonspace.in

Resolution chain

IPv6 resolution

No AAAA record for pentagonspace.in is recorded in WhisperGraph.

Attribution

atria convergence

ORIGIN_AS

WHOIS identity

Registrar
iana:146
Registrant organisation
pentagon space pvt

Subdomains

Subdomain
admin.pentagonspace.in
bd.pentagonspace.in
bdcv.pentagonspace.in
bdincub.pentagonspace.in
bdlead.pentagonspace.in
bdm.pentagonspace.in
blogs.pentagonspace.in
chatters.pentagonspace.in
collector.pentagonspace.in
counselor.pentagonspace.in
cub.pentagonspace.in
cvj.pentagonspace.in

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

  • pns101.cloudns.net
  • pns102.cloudns.net
  • pns103.cloudns.net
  • pns104.cloudns.net
  • 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

MX records

  • smtp.google.com

Threat-feed evidence

History

Related pages

Pivot from pentagonspace.in 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: "pentagonspace.in"})-[: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.