Skip to content

Hostname

inintca.com

Last fetched

inintca.com resolves to 100.50.208.183, announced in 100.48.0.0/12 by AMAZON-AES - Amazon.com, Inc. in US. inintca.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 · inintca.comRouting diversity1.5/10Peering density7.1/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/inintca.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:468
Registrant organisation
on behalf of inintca.com owner
Contact emails
scott.workman@inin.com, 124ad7be-9bf9-4659-8d15-d893ad2c9655@identity-protect.org, 29184354-53f2-488b-82a0-acd53e5d8f88@identity-protect.org, 43258bb8-f4f2-49fb-9843-9083b114a06a@identity-protect.org, 878a3e97-e994-4e33-9a17-4e0063d84b2d@identity-protect.org, d1083758-6adc-40a1-96ed-257a74d0ebe2@identity-protect.org, e73283ca-2223-4563-8d66-a7a169225713@identity-protect.org, owner-10846331@inintca.com.whoisprivacyservice.org, owner-2644476@inintca.com.whoisprivacyservice.org

Subdomains

Subdomain
apps.inintca.com
beyond.inintca.com
bridge.inintca.com
byoc.inintca.com
de-help.inintca.com
edge-proxy.inintca.com
es-help.inintca.com
fr-help.inintca.com
infrastructure.inintca.com
jp-help.inintca.com
login.inintca.com
pairing.inintca.com

Showing 12 of 34. View all subdomains →

Mail and authentication

Nameservers

  • ns-214.awsdns-26.com
  • ns-939.awsdns-53.net
  • ns-1321.awsdns-37.org
  • ns-1647.awsdns-13.co.uk

MX records

  • inbound-smtp.us-east-1.amazonaws.com

SPF policy

  • include: amazonses.com

Threat-feed evidence

History

Related pages

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