Hostname
twomen.com
Last fetched
twomen.com resolves to 18 IPv4 addresses operated by AMAZON-02 - Amazon.com, Inc. in US. WHOIS lists iana:468 as the registrar.
Nutrition Label
Resolution chain
twomen.com resolves to 18 distinct IPv4 addresses via WhisperGraph DNS data. Each row links to the IP, prefix, and announcing ASN.
WHOIS identity
- Registrar
- iana:468
- Organization
- on behalf of twomen.com owner
- Contact emails
- marianne.list@twomenandatruck.com
- 15ae0363-0bfd-4904-984e-91eb7e173b48@identity-protect.org
- 1fba32ad-9208-4a8d-b562-d32416a6df74@identity-protect.org
- 5fede8cb-07ed-4e79-8bbe-0cf6bbccd2e2@identity-protect.org
- 8a0c6ef4-8bf4-4ed2-950d-73952a723777@identity-protect.org
- 9c2a82af-6dd8-4527-bb5f-8f119a0295c1@identity-protect.org
- d24c9659-0c71-4d84-a850-0b98203200c6@identity-protect.org
- owner-11342081@twomen.com.whoisprivacyservice.org
- owner-3067490@twomen.com.whoisprivacyservice.org
- owner-6757689@twomen.com.whoisprivacyservice.org
- owner-7381933@twomen.com.whoisprivacyservice.org
- owner-7994398@twomen.com.whoisprivacyservice.org
Subdomains
51 observed subdomains of twomen.com.
Showing 25 of 51. View all subdomains →
Web-graph footprint
Distinct hostnames that link to or from twomen.com in the public web crawl.
71 sites link to this hostname.
Threat posture
History
Mail and authentication
MX records
SPF policy
4 SPF mechanisms authorising senders for twomen.com.
| Mechanism | Target |
|---|---|
| SPF_INCLUDE | mail.zendesk.com |
| SPF_INCLUDE | spf.protection.outlook.com |
| SPF_IP | 205.145.138.131 |
| SPF_IP | 72.13.13.17 |
Related pages
Pivot deeper into the graph from twomen.com.
- IP · 16.58.138.153
- ASN · AS16509AMAZON-02 - Amazon.com, Inc.
- Registrar · iana:468
- Country · US
- Email · marianne.list@twomenandatruck.com
- TLD · .com
- Browse hostnames · tw…
- Glossary · What is a hostname?
- Whisper Internet Directory — home
- Live MOAS conflicts feed
- Threat feed · Spamhaus DROP
- United States internet infrastructure
Cypher and MCP
Reproduce the resolution chain directly against graph.whisper.security:
MATCH (h:HOSTNAME {name: "twomen.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
-[:ROUTES]->(asn:ASN)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, asn.name AS asn, n.name AS operator
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.