Skip to content

Hostname

vortexsoftware.com

Last fetched

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

Resolution chain

IPv6 resolution

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

WHOIS identity

Registrar
iana:1068
Registrant organisation
dennis derrick
Contact emails
dbderrick@hotmail.com, c84e4a711cf04185b0cbfed2db5565a4.protect@withheldforprivacy.com

Subdomains

Subdomain
admin.vortexsoftware.com
api.vortexsoftware.com
assets.vortexsoftware.com
blog.vortexsoftware.com
client-api.vortexsoftware.com
collector.vortexsoftware.com
docs.vortexsoftware.com
domain-redirector.vortexsoftware.com
login.vortexsoftware.com
profiler.vortexsoftware.com
renderer.vortexsoftware.com
track.vortexsoftware.com

Showing 12 of 14. 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-70.awsdns-08.com
  • ns-348.awsdns-43.com
  • ns-919.awsdns-50.net
  • ns-926.awsdns-51.net
  • ns-1453.awsdns-53.org
  • ns-1500.awsdns-59.org
  • ns-1657.awsdns-15.co.uk
  • ns-1943.awsdns-50.co.uk

MX records

  • smtp.google.com

SPF policy

  • include: amazonses.com
  • include: _spf.google.com

Threat-feed evidence

History

Related pages

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