Skip to content

Hostname

invertexto.com

Last fetched

invertexto.com resolves to 54.207.65.61, announced in 54.207.0.0/17 by AMAZON-02 - Amazon.com, Inc. in BR. invertexto.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 · invertexto.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/invertexto.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of invertexto.com owner
Contact emails
dominios@minihost.com.br, feramal@gmail.com, 22cdd2e1-5816-47a6-b749-005976d76548@identity-protect.org, 2621c325-261e-4418-a517-45518f01d9dc@identity-protect.org, 65ba3921-1aed-4f5e-a15b-b68a3979c70d@identity-protect.org, 6c988285-d41a-4ee2-bf4a-60643d7f3ad0@identity-protect.org, 8a1aa3f9-e52d-4227-9872-c4f24de687ee@identity-protect.org, cdb4e926-628c-4436-8be6-659bdaf3ab5b@identity-protect.org, d82b03ba-01bc-48f8-91ea-4bdd8b4836d2@identity-protect.org, owner-4215265@invertexto.com.whoisprivacyservice.org, owner-4834171@invertexto.com.whoisprivacyservice.org, owner-6787934@invertexto.com.whoisprivacyservice.org, owner-8524370@invertexto.com.whoisprivacyservice.org

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

  • ns-94.awsdns-11.com
  • ns-940.awsdns-53.net
  • ns-1155.awsdns-16.org
  • ns-1602.awsdns-08.co.uk

MX records

  • mx.zoho.com
  • mx2.zoho.com

SPF policy

  • include: amazonses.com
  • include: zoho.com

Threat-feed evidence

History

Related pages

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