Skip to content

Hostname

getos1.com

Last fetched

getos1.com resolves to 13.227.192.103, announced in 13.227.192.0/24 by AMAZON-02 - Amazon.com, Inc. in CZ. getos1.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 · getos1.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.3/10canon.whisper.security/host/getos1.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of getos1.com owner
Contact emails
42685e1c-f822-4c3f-9d5f-987464338fc3@identity-protect.org, 51a86c5f-d376-423f-b08a-92de041f6ca6@identity-protect.org, 71ddc604-aecb-4da8-a489-c38437640d68@identity-protect.org, 80a2d7d5-e500-4848-9a69-5e52294f0575@identity-protect.org, 8ec3e4c1-5d21-4855-a2d1-ee1102e47fa5@identity-protect.org, 97e28f9d-848c-4ec2-a464-207ef698de0a@identity-protect.org, e4f92404-75d2-407b-a5aa-1f2a2dffc13f@identity-protect.org

Subdomains

Mail and authentication

Nameservers

  • ns-190.awsdns-23.com
  • ns-776.awsdns-33.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
  • ns-1316.awsdns-36.org
  • ns-1727.awsdns-23.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

Threat-feed evidence

History

Related pages

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