Skip to content

Hostname

ownit.nyc

Last fetched

ownit.nyc resolves to 34.204.39.241, announced in 34.192.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. ownit.nyc 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 · ownit.nycRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.9/10canon.whisper.security/host/ownit.nyc

Resolution chain

IPv6 resolution

No AAAA record for ownit.nyc is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:9998
Registrant organisation
doitt
Contact emails
support@neustar.biz

Subdomains

Subdomain
www.ownit.nyc

Showing 1 of 1 subdomain (1 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.

Mail and authentication

Nameservers

  • pdns196.ultradns.biz
  • pdns196.ultradns.com
  • pdns196.ultradns.info
  • 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
  • pdns196.ultradns.net
  • udns1.ultradns.net
  • udns2.ultradns.net
  • pdns196.ultradns.org
  • pdns196.ultradns.co.uk

MX records

  • ownit-nyc.mail.protection.outlook.com

SPF policy

  • include: _spf.createsend.com
  • include: spf.protection.outlook.com
  • include: spf-0018ba01.pphosted.com
  • include: _spf.salesforce.com
  • ip: 156.154.134.1
  • ip: 156.154.16.225
  • ip: 156.154.17.104
  • ip: 156.154.17.216
  • ip: 156.154.24.226
  • ip: 156.154.25.104

Threat-feed evidence

History

Related pages

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