Skip to content

Hostname

os33.com

Last fetched

os33.com resolves to 89.106.200.1, announced in 89.106.200.0/24 by Enflow - Enflow B.V. in NL. os33.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 · os33.comRouting diversity1.5/10Peering density2.4/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint6.0/10canon.whisper.security/host/os33.com

Resolution chain

IPv6 resolution

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

Attribution

enflow

ORIGIN_AS

WHOIS identity

Registrar
iana:9
Registrant organisation
perfect privacy,
Contact emails
2a6e298e0a28fd0a676daa726a46113f@domaindiscreet.com, 51e937390a28fd0a789cca2a184b4b43@domaindiscreet.com, 57791045@myprivatename.com, 5ptio2n0vugl6822r13ascd0r9@domaindiscreet.com, a81be1660a28fd0a48f819eea774e2a8@domaindiscreet.com, be4618ca0a28fd0a3c8f0e188643adc3@domaindiscreet.com, defeed7e0a28fd0a64e8fbf662cb13aa@domaindiscreet.com, kd44y2de9c7@networksolutionsprivateregistration.com

Subdomains

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

  • ns20.digicertdns.com
  • ns10.dnsmadeeasy.com
  • ns11.dnsmadeeasy.com
  • ns12.dnsmadeeasy.com
  • ns13.dnsmadeeasy.com
  • ns14.dnsmadeeasy.com
  • ns15.dnsmadeeasy.com

MX records

  • os33-com.mail.protection.outlook.com

SPF policy

  • include: spf1.appriver.com
  • include: spf.mandrillapp.com
  • include: spf.protection.outlook.com
  • include: _spf.salesforce.com
  • include: mail.zendesk.com
  • a: zgateway.zuora.com
  • include: servers.mcsv.net
  • include: mailgun.org
  • ip: 142.147.8.10
  • ip: 142.147.8.115
  • ip: 142.147.8.116

Threat-feed evidence

History

Related pages

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