Hostname
texasenterprises.com
Last fetched
texasenterprises.com resolves to 20.25.232.11, announced in 20.0.0.0/11 by MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation in US. texasenterprises.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 20.25.232.11
20.0.0.0/11 · MICROSOFT-CORP-MSN-AS-BLOCK - Microsoft Corporation · Chicago, US
- 206.127.28.6
206.127.0.0/19 · SWITCH-LTD - SWITCH, LTD · Austin, US
IPv6 resolution
No AAAA record for texasenterprises.com is recorded in WhisperGraph.
Attribution
Github
saas · ORIGIN_AS
WHOIS identity
- Registrar
- iana:2
- Registrant organisation
- texas enterprises,
- Contact emails
- itsupport@alliedsalesco.com, txpo@worldnet.att.net
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- hank.ns.cloudflare.com
- ivy.ns.cloudflare.com
- ns10.dnsmadeeasy.com
- ns11.dnsmadeeasy.com
- ns12.dnsmadeeasy.com
- ns13.dnsmadeeasy.com
- ns14.dnsmadeeasy.com
- ns15.dnsmadeeasy.com
- 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
MX records
- us-smtp-inbound-1.mimecast.com
- us-smtp-inbound-2.mimecast.com
SPF policy
- ip: 207.211.31.120/32
- ip: 206.127.28.2/28
- include: mimecast.com
- include: us._netblocks.mimecast.com
- include: spf.protection.outlook.com
- a: spf.protection.outlook.com
- include: _spf.robly.com
- include: _spf3.robly.com
- include: spf.myconnectwise.net
- include: sendgrid.net
Threat-feed evidence
History
Related pages
Pivot from texasenterprises.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: "texasenterprises.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 20Or query Whisper from your own LLM workflow via the Whisper MCP server.