Skip to content

Hostname

alogoosht.com

Last fetched

alogoosht.com resolves to 185.106.200.198, announced in 185.106.200.0/24 by Netafraz - Netafraz Iranian Ltd. in IR. alogoosht.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 · alogoosht.comRouting diversity1.5/10Peering density1.9/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/alogoosht.com

Resolution chain

IPv6 resolution

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

Attribution

netafraz iranian

ORIGIN_AS

WHOIS identity

Registrar
iana:113
Registrant organisation
amirreza hadi
Contact emails
amirrezahadi@gmail.com, info@efeh.com

Subdomains

Subdomain
assets.alogoosht.com
cms.alogoosht.com
db.alogoosht.com
mail.alogoosht.com
ms.alogoosht.com
next.alogoosht.com
oms.alogoosht.com
pms.alogoosht.com
www.alogoosht.com

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

Sample outbound links

Mail and authentication

Nameservers

  • 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.liara.zone
  • ns2.liara.zone

MX records

  • mail.alogoosht.com
  • c1.liara.email
  • ns1.liara.zone
  • ns2.liara.zone

SPF policy

  • a: alogoosht.com
  • mx: alogoosht.com
  • include: spf.c1.liara.email

Threat-feed evidence

History

Related pages

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